Short answer
There is not enough verified, like-for-like data to name the best Ride A Pet pet or publish a trustworthy tier list. The official game description supports one clear selection goal: faster pets help you search for rarer eggs. A secondary guide also describes placing pets to earn money, but the earning rules and pet-by-pet values have not been independently verified.
Kitsune, Phoenix, and Dragon each have a community page name, which supports treating them as community-listed entities—not their current availability, acquisition method, rarity, speed, or income. Choose by the job you need done and by measurements from the same game version, rather than by an unsupported S/A/B ranking.
Before comparing pets
A useful comparison needs consistent conditions:
- Pick one purpose: reaching egg-search areas faster, completing a repeatable route, or testing the secondary guide’s claimed money-placement loop.
- Compare pets in the same server and current game version, on the same route, with the same mutations or other modifiers where possible.
- Record the pet name exactly as shown in game. Community page names alone do not prove that a pet is currently obtainable.
- Keep base performance separate from mutation performance. The available sources do not establish a normalized ranking method.
Named pet evidence table
| Pet | Verified scope as of September 16, 2026 | Acquisition status | Best-use verdict |
|---|---|---|---|
| Kitsune | A community wiki page with this name exists. Stats, rarity, and current-version availability are not verified. | Unknown; no checked source establishes an egg, odds, route, price, or requirement. | Unranked. Test only after confirming the pet appears in the current game and compare it on the same route as alternatives. |
| Phoenix | A community page name exists, but two secondary sources conflict sharply on both hatch chance and speed. | Unresolved. One competitor page estimates a 1–3% Flame Egg chance; a community page states 1 in 30T. The meanings, versions, and modifiers are not aligned. | Unranked. Conflicting speed figures use incompatible scales, so neither supports a best-pet claim. |
| Dragon | A community wiki page with this name exists. Stats, rarity, and current-version availability are not verified. | Unknown; no checked source establishes an egg, odds, route, price, or requirement. | Unranked. Confirm the entity in game before using it in a comparison. |
The table answers what the evidence can support. It is not a roster, acquisition guide, or tier list disguised as one.
How to choose for your goal
Goal: cover the map faster
- Choose a fixed route between two recognizable landmarks.
- Run it with each candidate under the same conditions.
- Time from the same start signal to the same finish point.
- Repeat enough times to catch obvious routing mistakes.
Success signal: one pet produces a repeatably shorter trip under matched conditions. That supports “faster for this route,” not “best overall.”
Failure branch: if results change widely, remove uncontrolled differences such as route deviations or mutations. If the game shows pet stats, capture the labels and units; do not compare values whose units differ.
Goal: support egg progression
The official description links faster pets with finding rarer eggs. Use the pet that makes your verified search-and-return route more reliable, then confirm that you can still interact with, carry, and hatch the target egg. No source currently establishes that Kitsune, Phoenix, or Dragon has a special egg-finding ability.
Success signal: the same route takes less time and still ends with the game’s hatch or objective-completion feedback.
Failure branch: if the route is faster but the egg cannot be collected, look for an in-game requirement message rather than assuming the pet is ineligible.
Goal: compare money production
A secondary guide says placed pets generate money, but current values, timing, capacity, and offline behavior are not verified. If that system appears in your build, compare equal observation windows and record the starting and ending totals.
Success signal: a repeatable difference under equal conditions.
Failure branch: if totals change because of another reward, upgrade, or collection event, discard the run. The current evidence cannot attribute that difference to the pet alone.
Why there is no tier list yet
A defensible Ride A Pet tier list would need a declared metric, current stats, acquisition cost or odds, mutation treatment, and version date. None of those is complete across the roster. Phoenix illustrates the problem: one secondary source gives a base speed range of 350–450 MPH, while another gives a base speed of 1M without a compatible unit. Choosing either number would manufacture certainty.
Until the data is normalized, use these evidence labels:
- Confirmed purpose: the official description says faster pets help search for rarer eggs.
- Community-listed name: Kitsune, Phoenix, and Dragon have community page names.
- Unverified performance: individual speed, income, rarity, and acquisition details.
- Conflicting claim: Phoenix odds and speed figures cannot currently be reconciled.
Evidence and update status
- Roblox experience description (
src-game) — checked September 16, 2026: confirms that rarer, faster pets are part of the egg-search progression loop. - Community wiki index (
src-wiki) — publication date unknown; checked September 16, 2026: supports only the existence of community page names for Kitsune, Phoenix, and Dragon. - All Things How guide (
src-guide) — published September 14, 2026; checked September 16, 2026: describes placing pets to generate money; the operation and values remain secondary and unverified by this site. - rideapet.wiki Phoenix page (
src-competitor-phoenix) — publication date unknown; checked September 16, 2026: supplies one set of Phoenix estimates. - Community Phoenix page (
src-wiki-phoenix) — publication date unknown; checked September 16, 2026: supplies incompatible Phoenix chance and speed claims.
Update this page only after current-version acquisition evidence and comparable pet stats are added to the shared ledger. A ranking requires consistent units and a stated use case, not just more names.