The Kruger S-65 Stingray is a single-seat medium fighter currently in late Alpha 4.10 PTU testing. Alpha 4.10 has reached Release Candidate testing, while Alpha 4.9 remains the current LIVE build. Interest is high because the ship combines a compact fighter layout, unusually heavy pilot-controlled guns, and very fast roll response. The important caveat is that current access was created as a short testing incentive, not as a permanent account unlock. Players following the wider patch can use the Star Citizen guide library to keep the ship in context with the rest of Alpha 4.10, but every Stingray-specific purchase decision should wait for an official store page.
S-65 Stingray Current Status
Cloud Imperium Games added the Kruger S65 Stingray to the All Waves Alpha 4.10 PTU build 12479687 as a new medium fighter. It remained part of the testing focus through later builds, including RC1 build 12497254. It was not a normal free-fly ship and was not automatically granted to every account. CIG used it as a reward for focused testing of several pieces of 4.10 content.
RSI's official PTU installation page currently lists Alpha 4.10 for the PTU and Alpha 4.9 for LIVE. That makes the distinction simple: seeing the S-65 in PTU footage does not mean that it is obtainable in the LIVE Persistent Universe.
| Status question | Verified answer |
|---|---|
| Is the S-65 flyable? | It was flyable in Alpha 4.10 PTU for accounts that received the temporary entitlement. Continued access after the original August 23 window is not guaranteed. |
| Is it in LIVE? | No. Alpha 4.9 remains LIVE while Alpha 4.10 is still in PTU Release Candidate testing. |
| Can every PTU player claim it? | No. The original incentive was limited to eligible testers, and its announced free-access window has ended. |
| Does PTU access add it permanently to My Hangar? | No. A temporary PTU entitlement is not an account pledge and can be removed. |
How Players Got the S-65 Stingray in the PTU
The official Alpha 4.10 PTU patch notes for build 12479687 gave two routes. Accounts that had already contributed substantial testing time could receive the Stingray immediately. New testers could qualify by completing one of three activity requirements in that PTU environment:
- Complete three Cargo Missions.
- Complete the instanced Siege of Orison event.
- Complete one Recco Battaglia story mission.
Only one route was required. Completing all three did not create three ships or convert the test access into a permanent pledge. CIG also stated that the entitlement was applied manually, so it could take time to appear after the qualifying activity. The original criteria can be checked in the official Alpha 4.10 PTU patch notes.
During the active incentive period, entitled accounts could find the ship in the PTU ASOP terminal list after the manual grant had been processed. Restarting the launcher or checking another ASOP terminal could help distinguish a delayed grant from a local terminal problem. Re-copying an account to PTU was a poor first troubleshooting step because it reset the test account and could remove progress used to satisfy the qualification requirement.
Get any Star Citizen service from ExpCarry: raids, dungeons, PvP, leveling, gold, farming, coaching, and custom orders.
Is the Temporary PTU Access Still Available?
The public stress-test announcement said granted players could fly the Stingray free through Sunday. That announcement was posted on August 19, and the relevant Sunday was August 23, 2026. That announced access window has now passed, and no public extension has been confirmed.
An entitlement may remain visible briefly because PTU services and account grants are not always removed at exactly the same moment. That does not establish continued eligibility. Repeating the old activity checklist after the published window should not be expected to unlock the ship unless CIG explicitly reopens the incentive in newer patch notes. If the ship is still present on an account, treat that access as temporary.
S-65 Stingray Price and Expected Sale
There is no confirmed S-65 Stingray pledge price, Warbond price, upgrade value, rental price, or aUEC purchase price at the time of writing. CIG has also not published a standalone sale date. Any dollar amount circulating before the official ship page opens is an estimate, leak, or guess rather than a price players can rely on.
A sale close to the Alpha 4.10 LIVE release is plausible because CIG often opens sales for newly released ships, but that pattern is not a promise. The Stingray could instead appear during a later event, arrive with different packages, or remain unavailable for a period. It is equally important not to assume immediate in-game purchase availability. New pledge ships usually reach in-game dealerships later, but CIG does not guarantee one fixed delay for every vehicle.
| Price type | Current status | What would confirm it |
|---|---|---|
| Standard pledge | Unannounced | An RSI pledge-store or ship page |
| Warbond pledge | Unannounced | An official cash-only offer |
| CCU value | Unannounced | The official Ship Upgrades interface |
| In-game aUEC price | Not listed | A LIVE dealership listing |
Once an aUEC price actually exists, a current ship-price database is more useful than an old launch estimate. The Star Citizen aUEC calculator deliberately excludes ships without a valid in-game purchase offer, which is the correct behavior for the S-65 right now.
S-65 Size, Crew, and Combat Role
CIG officially calls the Stingray a medium fighter. The PTU version has one pilot seat, no co-pilot station, and no meaningful cargo role. A small access area and personal weapon storage do not turn it into a daily transport. It is designed around direct combat, short preparation time, and pilot-controlled firepower.
Official length, beam, height, landing footprint, and mass have not yet been published on an RSI vehicle page. This is one area where repeating a datamined bounding box would create false precision. The ship also changes its external configuration between different states, so a single unofficial screenshot measurement would not reliably answer hangar or carrier-fit questions.
Until the official specification page appears, owners of compact carriers should assume that the S-65 needs medium-fighter clearance rather than treating it like an Arrow-sized light fighter. Test the landing configuration in the exact hangar or ship bay before relying on it operationally. Dimensions are especially likely to receive metadata corrections before LIVE even when the visible model does not change.
Current S-65 Stingray PTU Stats
The following figures reflect the current Alpha 4.10 PTU configuration and extracted build data rather than a final RSI technical sheet. The latest RC1 patch notes still do not provide a finished public specification page, so these values remain useful for understanding the ship's present behavior but can change before or after the LIVE release.
| Category | Current PTU value | Confidence note |
|---|---|---|
| Role and crew | Medium fighter, 1 pilot | Role is confirmed by CIG; seat count is visible in the test ship. |
| SCM speed | About 218 m/s | PTU build value; not final. |
| Forward boost speed | About 485 m/s | PTU build value; conditions and tuning can change it. |
| NAV maximum speed | About 1,200 m/s | PTU build value; not a combat-speed rating. |
| Pitch, yaw, roll | About 55, 42, and 185 degrees per second | The high roll rate is the standout characteristic. |
| Shield generators | 2 Size 1 | Current test configuration. |
| Power plant | 1 Size 1 | Current test configuration. |
| Pilot guns | 4 Size 2 and 2 Size 4 Kruger weapon positions | Current PTU configuration; fitting permissions can still change. |
| Missile capacity | 2 Size 4 racks, each carrying 4 Size 2 missiles | Eight Size 2 missiles in the current build data. |
CIG has already made significant survivability changes during the PTU cycle. Build 12488012 increased the Stingray's armor protection and reduced penetration damage reaching internal components. RC1 build 12497254 then included additional fixes aimed at incorrect cockpit damage behavior and a tail section that was not being protected properly by the ship's shields. These changes are a strong warning against treating any early hull-health or armor value as permanent.
Weapons and Support Systems
The headline feature is the six-gun pilot battery. The four Size 2 and two Size 4 weapon positions give the Stingray much more forward gun potential than its slim profile suggests. The PTU ship uses Kruger-specific weapon installations, so players should verify actual Vehicle Loadout Manager permissions in the current build instead of assuming that every weapon position can accept any normal gun of the same size.
The two missile racks provide eight Size 2 missiles in total. Missile slots are the more realistic area for role-specific tuning if the current editing permissions survive to LIVE. A mixed seeker package can reduce the chance that one countermeasure response defeats the entire salvo, while a uniform package makes firing discipline and lock behavior easier to learn. Because missile balance and countermeasures change frequently, the best choice is the seeker type that works reliably in the current build, not an old meta list.
Two Size 1 shields provide split-generator redundancy, but they do not make the Stingray durable under sustained focus fire. One Size 1 power plant also means that power damage can end the fight quickly. The ship rewards a pilot who preserves shields, controls exposure, and leaves before a damaged component becomes a total loss.
Best S-65 Stingray Loadout
The best all-round PTU approach is still close to stock. The ship remains under active balancing, its weapon fitting is unusually specialized, and the value of buying expensive replacement components is low when a PTU account reset or build update can erase them. Start by confirming which slots are actually editable in the current patch rather than purchasing parts from a loadout made for an earlier build.
| Slot or system | Recommended approach | Reason |
|---|---|---|
| Kruger guns | Keep the installed set unless the current VLM explicitly allows a useful alternative | Weapon compatibility is more restricted than on a conventional fighter and can change during testing. |
| Shields | Favor dependable regeneration and sufficient power headroom | The ship survives by resetting engagements, not by trading hull damage. |
| Power plant | Prioritize stable output and durability if the slot is editable | A single plant is a critical failure point, and six energy guns can make power management important. |
| Missiles | Use eight Size 2 missiles with either mixed seekers or one familiar lock type | Both approaches are valid; consistency matters more than a theoretical paper advantage. |
| Quantum drive | Choose for the routes actually flown | A combat ship gains little from a fast drive if its fuel economy cannot complete the planned trip. |
In combat, begin with balanced power, then move additional allocation to weapons only during a clean firing window. Shift power back toward shields while extending or rotating away from the target. Six energy guns can punish careless power use, so an uninterrupted trigger hold is rarely the best answer. Fire in controlled windows, watch capacitor recovery, and use the Stingray's speed to create the next pass.
For players planning a broader fighter progression rather than one temporary test ship, the Star Citizen hub provides a useful reference point for ships, current tools, and assisted gameplay options. It should not be used as evidence that an unreleased Stingray can already be bought or permanently delivered.
Handling and Flight Technique
The current Stingray feels roll-dominant. Its reported roll rate is far higher than its yaw rate, so efficient turns come from rolling the lift vector toward the target and then pitching. Trying to follow a fast opponent with flat yaw wastes the ship's strongest rotational axis and makes its handling feel less agile than it is.
The high forward boost speed supports short attack runs, separation, and shield recovery. It does not mean the ship should remain at maximum boost throughout a duel. Boost is a limited tactical resource, and arriving fast without enough control authority can carry the pilot through the firing solution. Use it to change range or deny an opponent's angle, then return to a speed where the nose remains precise.
The S-65's firepower encourages head-on confidence, but two Size 1 shields are still a relatively light defensive layer for a medium fighter. Avoid extended jousts against ships with stronger shield pools or high ballistic pressure. The better pattern is to make a high-quality pass, roll and pitch into the next angle, then break contact when shields or power state stop supporting the exchange.
S-65 Stingray vs Closest Competitors
The S-65 sits between agile light fighters and more conventional medium combat ships. Direct comparisons remain provisional because the Stingray is still in PTU while its rivals have longer LIVE balance histories.
| Ship | Why it is comparable | Where the Stingray appears stronger | Where the rival is safer |
|---|---|---|---|
| Anvil F7C Hornet Mk II | Single-seat medium fighter with strong forward weapons | More distinctive roll-focused handling and a highly integrated six-gun layout | A more established ecosystem and a clearer conventional fitting path |
| Aegis Sabre | Single-seat medium fighter built around controlled engagements | Higher apparent direct gun ceiling in the tested configuration | Stealth-oriented signature management and a mature role |
| Drake Buccaneer | Compact high-output fighter that trades comfort for aggression | Better roll authority and a more integrated weapons package | Known LIVE availability, pricing, and fitting behavior |
The Hornet Mk II is the strongest comparison for a buyer who wants a mainstream medium fighter. The Sabre is more suitable when signature control is the main strategy. The Buccaneer is relevant for pilots who want compact firepower and do not need the newest design. The Stingray's case is strongest for players who specifically enjoy its handling and Kruger weapon concept, not for anyone simply chasing the latest stat advantage.
Common S-65 Problems in PTU
The ship did not appear after a qualifying mission. During the original incentive, the grant was manual and could be delayed. Players had to complete the activity in the correct PTU build and within the announced eligibility window. Completing those old requirements after the window has ended should not be expected to produce a new entitlement.
The ship disappeared after an update or account copy. This is expected behavior for a temporary PTU entitlement. A recopy can rebuild the test account from its source data, while a new PTU build can change or remove promotional grants.
A weapon or component cannot be changed. The Stingray uses specialized Kruger weapon positions, and not every apparent hardpoint necessarily behaves like a conventional unrestricted mount. Check the in-game loadout manager rather than relying on a third-party planner that has not yet imported the current PTU definition.
The ship feels slow when turning. Use roll followed by pitch instead of relying on yaw. The difference between its strong roll rate and lower yaw rate is large enough to change how it should be flown.
Repair, refuel, or claim behavior is inconsistent. Test builds can have backend and ASOP faults unrelated to the individual ship. Store the vehicle if possible, try another station, and check the current Issue Council before repeatedly claiming or recopying the account.
What Can Change Before the LIVE Release?
Almost every numeric part of the Stingray can still change: SCM and boost speeds, rotation rates, armor, component penetration, gun output, shield behavior, missile selection, fuel capacity, and claim time. CIG has already changed its armor and internal component survivability during the PTU cycle and continued fixing cockpit and tail-section damage behavior in RC1, showing that the current configuration remains active test data rather than a locked launch specification.
The official S-65 PTU stress-test announcement frames access as part of testing and feedback collection. That context matters. Community extraction is useful for measuring one build, but later official patch notes, the LIVE vehicle page, and the pledge store should override every provisional number in this guide.
S-65 Stingray FAQ
These short answers cover the questions most likely to change as the ship moves from PTU testing toward a possible LIVE release. Status and pricing should be checked against RSI whenever Alpha 4.10 moves to LIVE or a new store page appears.
Can I buy the S-65 Stingray now?
No official pledge sale or in-game dealership listing has been confirmed. PTU access was a temporary testing entitlement, not a purchase.
How did players unlock the S-65 in PTU?
Eligible accounts either had substantial prior PTU participation or completed three Cargo Missions, one full Siege of Orison run, or one Recco Battaglia story mission during the announced incentive. Entitlements were applied manually.
What is the Star Citizen Stingray price?
The pledge, Warbond, CCU, rental, and aUEC prices are all unannounced. A precise amount shown without an official RSI listing should be treated as speculation.
What weapons does the S-65 have?
The current PTU configuration indicates four Size 2 and two Size 4 pilot weapons, plus two Size 4 missile racks carrying four Size 2 missiles each. The ship uses specialized Kruger weapon installations, and fitting permissions can still change before LIVE.
What is the best Stingray loadout?
Stay close to the tested stock setup, protect power headroom, favor reliable shield recovery, and choose missiles for the targets and countermeasures in the current build. Expensive PTU component shopping is difficult to justify while persistence, fitting permissions, and balance remain temporary.
Is the S-65 better than the Hornet Mk II?
Not universally. The Stingray currently offers distinctive roll-heavy handling and an integrated six-gun package. The Hornet Mk II has a more established role and fitting ecosystem. Pilot style and future balancing will decide which is better for a particular job.
Conclusion
The Kruger S-65 Stingray is a promising one-seat medium fighter, but it remains a PTU test ship rather than a finished retail product. Alpha 4.10 has reached RC1 build 12497254, while Alpha 4.9 remains LIVE. The Stingray's temporary access was tied to specific Alpha 4.10 participation, and the announced free-test window ended on August 23. No official price, sale date, LIVE deployment, or final dimensions have been published.
Current PTU data points to a fast, roll-focused fighter with two Size 1 shields, a single Size 1 power plant, six pilot guns, and eight Size 2 missiles. CIG has already changed its armor and component survivability during testing, so those numbers explain how the ship behaves now rather than defining a permanent launch configuration. Anyone considering a real-money purchase should wait for the official LIVE specifications, pledge-store price, and confirmed long-term fitting rules.
