Jump to content

Vancouver: T-Comm "E-Sightings"


MCW Metrobus
 Share

Recommended Posts

Sorry, there's a configuration issue with the server that I haven't been able to trace yet. It's unrelated to the 15000s being put into service, but unfortunately coincides at the same time. I am aware of the issue and am trying to resolve it as soon as possible but until then T-Comm may be up and down.

While I'm here I'll post this esighting..

Screenshot_2016-02-03-18-11-43.png

Link to comment
Share on other sites

  • 4 weeks later...

Seems like BTC stopped doing rush-hour 41s.

I don't think BTC has done rush hour 41s for at least a couple of sheets now. I did a lot of 41 mid runs last sheet and never saw a BTC bus on that route. There was at least one BTC 49 in the afternoon though.

Link to comment
Share on other sites

There was at least one BTC 49 in the afternoon though.

Yeah, that one runs in the PM (as an EB express?) then turns into a 106 to new west and back. I recall a while ago that it would do an extra 144, making that one of the few blocks that touched UBC and SFU in one day.

Link to comment
Share on other sites

Yeah, that one runs in the PM (as an EB express?) then turns into a 106 to new west and back. I recall a while ago that it would do an extra 144, making that one of the few blocks that touched UBC and SFU in one day.

Those 49 trippers start at Cambie and 49th or dunbar so the UBC part isn't technically true unless this one is special... (9409 did http://tcomm.bustrainferry.com/mobile/block/1428670)

That got me interested; I found this one (UBC run is past midnight so if you were perverse you could say it still doesn't count)

http://tcomm.bustrainferry.com/mobile/block/1429115

..otherwise I really can't think of any that would satisfy that criteria.

Link to comment
Share on other sites

Not sure if anyone has pointed this out before, but there seems to be some discrepancy with reported times. I realize the issue most likely lies with the GPS trip logger TransLink is using. I've attached a screenshot showing the two instances where I noticed it. It probably happens more often but I've never checked before.

I know the Compass times are correct because I texted NB at 5:13, so the bus couldn't have been there at 5:10. If the problem is indeed caused by TransLink, I wonder if it affects 33333 and/or the mobile NB site.

I'm sure someone with more knowledge on the real-time GPS system and/or T-Comm can shed some light on this.

times.png

Link to comment
Share on other sites

If you look at a trip or a block on Tcomm, it shows scheduled times, not actual times. So, the 100 was simply a couple of minutes late at those stops. Texting the bus stops will you give you the actual times.

Not sure if anyone has pointed this out before, but there seems to be some discrepancy with reported times. I realize the issue most likely lies with the GPS trip logger TransLink is using. I've attached a screenshot showing the two instances where I noticed it. It probably happens more often but I've never checked before.

I know the Compass times are correct because I texted NB at 5:13, so the bus couldn't have been there at 5:10. If the problem is indeed caused by TransLink, I wonder if it affects 33333 and/or the mobile NB site.

I'm sure someone with more knowledge on the real-time GPS system and/or T-Comm can shed some light on this.

Link to comment
Share on other sites

I think that run may get a change to an artic at kootnay loop before heading downtown

Sent from my SM-T700 using Tapatalk

No it stays as a 40ft. There really isn't a need for artics on that run. Only time N17 goes 60ft is interlined with 99, maybe a 135, but I'm pretty sure it's 135/N35 and an additional N19 on some runs.

Link to comment
Share on other sites

Yeah, that one runs in the PM (as an EB express?) then turns into a 106 to new west and back. I recall a while ago that it would do an extra 144, making that one of the few blocks that touched UBC and SFU in one day.

The BTC one is not an Express (goes via 54th) and operates from Dunbar Loop to Metrotown. It's a school tripper. There are a few "express" ones that start at UBC, one for sure is a VTC one (rode it the other day and driver missed the turn onto 16th forgetting he wasn't a 41 anymore). I think there is at least one other express from UBC but it's RTC and there are several RTC express trips that start from Cambie. The VTC one from UBC does I think 2 Cambie to Metrotown express trips afterwards. I think there's also a westbound VTC one on a 32 line group, but I haven't been able to confirm that lately so it's possible it's an RTC tripper now (think I saw a "Dunbar Loop" artic westbound in peak hours that was around that time, but unsure if there's another).

I haven't seen too many out-of-depot trippers recently, other than the ones mentioned above. As previously mentioned, there used to be some BTC 41s in the afternoon, and at least 1 RTC 41 in the morning. I remember an RTC 25 at one point too that I rode on, and a couple BTC 25s.

Link to comment
Share on other sites

No it stays as a 40ft. There really isn't a need for artics on that run. Only time N17 goes 60ft is interlined with 99, maybe a 135, but I'm pretty sure it's 135/N35 and an additional N19 on some runs.

When I first started, I worked out of BTC and a couple of times I drove the 135 block that did both an N35 round and a one-shot on N19. The 135 would turn into an N35 at SFU a little after 1 am, do a round-trip into downtown and back, then deadhead downtown and become (what was then the last) N19 to Surrey. The late 99s turn into N17s, and last sheet one of them also did an N20. Not sure if that still exists. (I tried to sign that one on the spareboard once...)

Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...

9651 was booked out on 15/27 yesterday however after breaking down and before getting switched out for 9642 shortly after 21:15, we came to realize, it never showed up on T-Comm online nor did T-Comm in Surrey have any clue the bus was in service.

Link to comment
Share on other sites

  • 1 month later...

With each service change, here are a few interesting blocks I found

This one with a 354 coming off 401s and 410s
http://www.tcomm.bustrainferry.com/mobile/bus?busId=7438

This one with 4 trolley routes
http://www.tcomm.bustrainferry.com/mobile/bus?busId=7258

This artic block with 49, 430, and 404
http://www.tcomm.bustrainferry.com/mobile/bus?busId=12016

Link to comment
Share on other sites

7 hours ago, Express691 said:

With each service change, here are a few interesting blocks I found

 

This one with a 354 coming off 401s and 410s

http://www.tcomm.bustrainferry.com/mobile/bus?busId=7438

 

This one with 4 trolley routes

http://www.tcomm.bustrainferry.com/mobile/bus?busId=7258

This artic block with 49, 430, and 404

http://www.tcomm.bustrainferry.com/mobile/bus?busId=12016

That's some weird interlines.  Optimization at its best no doubt.  Didn't realize the 430 needed artic's at any time of the day.  

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...