Start with the official network
Buenos Aires Ciudad publishes visitor and transport information, while SUBE is the official starting point for the card used across participating public transport. Read current instructions for obtaining, loading, and using a card. Keep the address and destination written clearly, and ask about direction, transfer, and final walking segment.
SUBE instructions cover the card system, while Buenos Aires Ciudad covers city transport information. Read both for the current route and payment context. Write the destination, direction, transfer, and last walking segment in a form a station worker or driver can recognize.
SUBE is part of the practical first week, but learning the card is only one step. Pair its current instructions with the city route and the exact address. Write down where to obtain or load the card and what a traveler will do if a machine or phone fails.
Test the whole journey
Ride the route at the time you would actually leave and return. Measure the walk, waiting, boarding, transfer, and final walk. Note how you would handle rain, a missed connection, or an interruption. A generic estimate cannot account for a stroller, mobility aid, child, heat, or an unfamiliar crossing.
Test a trip at the hour it will repeat and time every stage. A route with one transfer can still fail because of a long walk, stairs, crowding, or a missed connection. Keep a second route and a contact who knows the address, especially during the first weeks.
A route test should include the walk to the stop and the final doorway. Time the transfer, notice platform or pavement barriers, and repeat the trip in the likely weather. Keep a route card with destination, direction, and a backup so a new rider does not need to improvise.
Plan for access and payment
Check the route for stairs, platform gaps, narrow pavements, and current lift or ramp information. Ask the city or service operator about a barrier affecting a particular trip. Learn how to load and protect the SUBE card and keep a backup payment option that works for your circumstances.
Ask about a lift, ramp, platform, vehicle, or construction barrier with the operator or city channel. Do not infer accessibility from a map icon. Protect the SUBE card and keep a backup payment method that works when a phone, card, or top-up location is unavailable.
Access needs require a direct question to the operator or city channel. Ask about a lift, ramp, or vehicle. Ask about a transfer or temporary closure. Record the answer date. A map may show a station while omitting a broken elevator or a difficult crossing.
Recheck before a recurring commute
Review the official city transport page and current SUBE information before a school term, new job, move, or long trip. Check closures and planned works close to departure. Transport conditions change, and this guide cannot promise availability or accessibility at a particular time.
Recheck service notices before a school term, new job, or airport trip. A current map does not promise that an elevator or route is working on the day. Allow buffer time while learning the network and record the service contact for a disruption that matters.
Recheck notices before the journey and allow a buffer while learning. If the commute will repeat, compare it with the home's other services and the household's energy. The best route is the one the person can use consistently, with a realistic fallback when the network changes.
Common questions
What is SUBE?
SUBE is Argentina's public transport card system. Use the current official SUBE information for card, loading, and service instructions.
Can a map guarantee an accessible Buenos Aires route?
No. Test the full route and confirm current accessibility information because lifts, crossings, and construction can change.
What belongs in a Buenos Aires route backup?
Keep a second route, a written destination, a way to recharge or replace a payment method, a phone contact, and enough time to walk or wait. For a mobility or family need, confirm the backup's barriers too. A backup that cannot be used by the traveler is not a practical backup. Write the fallback for the traveler who will actually make the trip, including any access or language need.