The R2 now reaches Metrotown from Phibbs Exchange, via Hastings Street and Willingdon Avenue. That is a meaningful new link across the North Shore, Vancouver and Burnaby — and a reason to pause before making the usual transit shortcut: seeing “RapidBus” on a map and assuming every trip will be faster.
TransLink launched the extension on September 7 as all-day, seven-day service. It replaced the weekday-peak-only #222, adds a limited-stop connection through Brentwood and Metrotown, and changes the shape of the corridor for many #130 riders. Most #130 trips now start and end at Kootenay Loop; only a small number of peak-hour trips continue to Phibbs Exchange.
The useful way to think about the R2 is less “a faster bus” and more “a new corridor with different choices.” A one-seat ride may remove a transfer for some journeys. It does not guarantee a quicker door-to-door trip, a particular connection, or a smooth ride on a specific day. Traffic, service conditions, stop locations and the next leg of the journey still do a lot of the work.
What changed — and what it does not promise
| What changed | What it does not promise |
|---|---|
| The R2 links Phibbs Exchange, Brentwood and Metrotown, running via Hastings and Willingdon. | Every end-to-end trip will be predictably quicker. |
| The former #222 service was discontinued and the R2 took over that corridor role. | The route name alone confirms the destination sign, stop or current service state. |
| Most #130 trips now start and end at Kootenay Loop; the #130 remains local service. | A #130 and an R2 are interchangeable for every trip. |
| The project lists eight added R2 stops. | Every stop is permanent or unchanged on the day of travel. |
| The service is called RapidBus. | It is the future Metrotown–North Shore BRT project, or that new Burnaby bus-priority or HOV lanes arrived with it. |
That last distinction is worth keeping straight. TransLink describes the extension as a near-term step ahead of future rapid transit: planning for Bus Rapid Transit and other options in this part of the region continues through a separate program with no final route selected, and the launch release states the R2 extension did not include changes to bus priority or HOV lanes in Burnaby. “RapidBus” describes the service; it should not become a promise about dedicated infrastructure that is not there.
The practical complication is physical as well as conceptual. TransLink says some permanent R2 stops were affected by adjacent development construction at launch, with temporary or existing stops in use at those locations until the permanent ones open. So a familiar route number is not enough. A rider can have the right route in mind and still be standing at the wrong curb, looking for a stop that has moved, or building a transfer around a service pattern that changed.
A copyable R2 trip card
Use this before a trip, especially if the route is new to you or the connection matters.
- Open the TransLink Trip Planner and check the travel date, direction and destination sign. Do not infer the specific trip from “R2” alone.
- Pick the service for the job. The R2 is limited-stop and connects Phibbs, Brentwood and Metrotown. The #130 remains the local option, with most trips starting and ending at Kootenay Loop.
- Confirm the physical stop and transfer before leaving. Check whether the stop is temporary, and leave room for a changed walking path or connection.
- Check TransLink Alerts immediately before departure. Check again after a material delay or missed connection rather than assuming the earlier plan still applies.
- For an accessibility-sensitive trip, verify the particular stop, alert state and full journey. A route description is a starting point, not a guarantee that every part of a trip will work as expected.
One useful comparison is to run the trip twice: once with the R2 in mind and once without assuming the route in advance. Read each itinerary as a proposal, not a promise. Check the walking leg, boarding stop and transfer it actually gives you. If the trip is hours away, repeat the check closer to departure instead of treating an earlier result as the final answer.
This is deliberately more cautious than a launch-day “best route” list. The best route depends on where a trip begins, the actual destination, timing and what the network is doing at that moment. A planner result plus the stop and alerts page is more useful than a confident-sounding generalization.
Who should take another look at their usual trip?
Former #222 riders are the obvious group: that route has been discontinued, so an old saved pattern needs a fresh check. Regular #130 riders should also look again because most trips now terminate at Kootenay Loop. And anyone transferring at Brentwood or Metrotown has a new option to compare against the combination they already use.
For occasional riders, the biggest win may simply be clarity. The R2 creates a legible north-to-south connection that reaches two major stations without asking every rider to construct the corridor from several route numbers. But clarity is not the same thing as certainty. A limited-stop route may be a better fit for one trip and the local service may be the sensible choice for another.
There is also no need to memorize a launch announcement. TransLink’s service changes page is the place to begin for the broader fall network change, while the Trip Planner and Alerts page are the better final checks for a real departure.
The R2 is a substantial addition to the map. Treat it as an invitation to redraw the trip — not as a blanket guarantee that the redraw is always faster. That small distinction is the difference between learning a new corridor and getting surprised by one.
