A useful Project Stardust ships list is a way to find the right hull, not a frozen count. Community category pages contain hundreds of ship-related entries, but those collections can include developer, event, meme, retired, or documentation pages alongside currently obtainable ships. The in-game tech tree is the reliable roster for your server and date.
Use this guide to move from franchise to faction, branch, tier, access, and role. It deliberately avoids claiming a permanent total or reproducing values that can change with balance updates.
Community corroborated — checked September 12, 2026: The roster spans Star Wars, Halo, Space Battleship Yamato, and Mass Effect families. Exact ships, branch positions, costs, and availability must be checked in the current tech tree.
Browse by franchise
Star Wars contains several community-documented faction paths, including Republic, CIS, Empire, Rebel, New Republic, and First Order themes. It is the broadest starting point when you want to compare brawlers, line ships, carriers, and longer-range options.
Halo centers on UNSC and Covenant branches. Community descriptions commonly contrast hull-focused UNSC designs and prominent spinal or missile pressure with shield-oriented Covenant designs, though every ship must be read individually.
Space Battleship Yamato includes UNCF, Garmillas, Gatlantis, and GUIA paths in community navigation. Players associate different parts of these trees with mobility, strong beam windows, or aggressive engagement plans.
Mass Effect currently has community references for Systems Alliance, Asari, Migrant Fleet, and Reaper branches. Broad tendencies include longer-range spinal pressure, shield defense, durable support, and sustained closer-range damage.
Browse by access type
Start by separating ordinary tech-tree ships from premium, event, test, developer, or otherwise special entries. A ship appearing in a community category does not prove that it is currently obtainable. Open its live node or purchase panel and identify the prerequisite and resource.
Starter ships are the safest way to sample a franchise. Tech-tree ships require progress along the displayed branch. Premium access may involve Gold or another current requirement. Event ships can be limited, rerun, or unavailable. Never assume an old event method still works.
If the current interface does not offer a purchase or unlock route, do not use an outside seller or script. Wait for an official return or creator announcement.
Browse by tier without treating tier as rank
Tier tells you where a ship sits in progression; it does not guarantee that the ship wins a particular matchup. Higher-tier ships can have larger profiles, slower rotations, more complex systems, and a greater cost when destroyed in value-weighted play.
When moving upward, compare the current ship and next ship in five areas: preferred distance, defense, mobility, firing arcs, and team job. If the next tier changes two or three of those at once, plan practice matches before applying a booster.
For the difficult later climb, follow the Tier IV to Tier V guide.
Browse by practical role
Use role tags as questions rather than rigid labels. A brawler needs a protected approach and enough survival to remain inside close pressure. An artillery or long-range ship needs sightlines and disciplined distance. A carrier manages craft while keeping the hull safe. A support hull adds screening, healing where available, interception, or presence. A line ship sustains team pressure without abandoning its retreat.
A ship can fill more than one role depending on mode, map, and current build. Read ship classes before trusting a community label.
Build your own current shortlist
Open the live tech tree and select three obtainable candidates. For each, record its franchise and faction, tier, resource requirement, primary defense, mobility, longest reliable weapon group, special systems, and one likely mode job.
Then remove any candidate whose path you do not enjoy. Compare several nodes leading to the other two. A branch is a repeated commitment, so the middle ships matter as much as the destination.
Play a starter or nearby ship from each remaining family. Keep mode and map in the note. Your shortlist should become smaller through real play, not larger through hype.
Verify a ship entry before spending
Confirm the ship name and node in the current tree. Read the cost icon rather than assuming it means Credits, Free XP, or Gold. Check prerequisites and whether the purchase is permanent, limited, or attached to an event.
Next open the stat and weapon panel. Review health, shields when present, speed and turn behavior, weapon arcs, range feedback, point defense, fighter capacity, and any spinal system. Use the ship stats guide to translate those fields into a match plan.
Finally ask where the ship retreats. If its strength requires an approach with no exit, the purchase may demand more map knowledge than you currently have.
Avoid misleading lists
A list is weak when it has no check date, mixes unobtainable and normal ships, omits factions, copies exact values without a version, or labels one hull “best” without a mode and role. Video rankings can be useful demonstrations, but verify their upload date and current interface.
Do not count community-category entries as playable ships. Do not infer availability from a thumbnail. Do not enter a private farming server to reach an unlock; the official game description prohibits farming servers and warns of resets or bans.
The best list is the live tree plus a decision method. It tells you what can be obtained now and whether the route fits the way you want to contribute.
Next step
After identifying a candidate, read its faction page in the factions hub, interpret its panel with ship stats, and match its job to modes. That turns a roster entry into a ship you can actually pilot well.