11 Sept 2022, 06:10 UTC≈2,890 viewsread 8 August 2026
This channel will be phased out (but not deleted), please follow @NUSOnTheMove for the latest ISB-related news!
Signed Ryan Ch’ng
Channel
The ISB Channel (Unofficial)
@nusisb
On this record: Growth · Engagement · Posts · Citations · Cite this entry
971subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001254672221 |
|---|---|
| Type | Channel |
| Username | @nusisb |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 25 August 2026 |
| On Telegram | t.me/nusisb |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 18:22 | 971 | -3 |
| 8 Aug 2026, 00:46 | 974 | no change |
| 7 Aug 2026, 22:40 | 974 | first reading |
Engagement
20 posts held, back to 5 July 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 11 September 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
31 Aug 2022, 00:36 UTC≈4,850 viewsread 8 August 2026
Did you know? Because of public transport distance fares, taking 95 from KR MRT to LT 27 may not add anything to your fare if you are coming from the MRT. Read more on how to check if this applies to you below! As always, if you see this because someone forwarded this to you, please join @NUSOnTheMove https://theisbman.home.blog/2019/01/17/is-95-free/
Signed Ryan Ch’ng
15 Aug 2022, 07:30 UTC≈3,090 viewsread 8 August 2026
Once again, please subscribe to @NUSOnTheMove and not this channel — all important updates will be posted there and not here moving forward (I will only occasionally forward to here)
Signed Ryan Ch’ng
8 Aug 2022, 02:39 UTC≈1,780 viewsread 8 August 2026
Forwarded from @NUSOnTheMove
Hello everyone and welcome to the official NUS On The Move channel! Subscribe for mobility-related updates in NUS, including ISB 🚌, parking 🚗 and more!
Signed Ryan Ch’ng
8 Aug 2022, 02:39 UTC≈3,360 viewsread 8 August 2026
[Announcement] Hi everyone, please subscribe to NUS Campus Services’ new channel at @NUSOnTheMove! I will post transport and mobility-related updates at the new channel instead of this one. This channel may continue for more personal matters and sharing of blog articles, but the live updates will now be official at the new channel. See you there!
Signed Ryan Ch’ng
4 Aug 2022, 00:25 UTC≈3,420 viewsread 8 August 2026
If you’re looking for the MPSH2 for student card matters: go to the UHC bus stop and follow the path away from the road, towards the expressway in the distance!
Signed Ryan Ch’ng
1 Aug 2022, 10:07 UTC≈3,060 viewsread 8 August 2026
Due to traffic congestion along South Buona Vista Road, services A1, D2, K and BTC will be delayed
Signed Ryan Ch’ng
1 Aug 2022, 00:08 UTC≈3,450 viewsread 8 August 2026
BTC 0800 trip is delayed due to traffic, will depart around 0810
Signed Ryan Ch’ng
31 Jul 2022, 23:28 UTC≈3,510 viewsread 8 August 2026
You may encounter app crashes with the NUS NextBus app. The developers are informed and working to restore functionality.
Signed Ryan Ch’ng
31 Jul 2022, 13:31 UTC≈3,450 viewsread 8 August 2026
Sticker
Sticker, posted without a caption
Signed Ryan Ch’ng
31 Jul 2022, 13:31 UTC≈3,060 viewsread 8 August 2026
Btw, my “ISB Routes” sticker pack has been updated with the new D1 route!
Signed Ryan Ch’ng
26 Jul 2022, 09:45 UTCviews —
The ISB Channel (Unofficial) pinned a photo
Showing the 12 most recent of 20 posts we hold for @nusisb. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 16 August 2026 — this entry's latest reading, not the date you are reading this.
“The ISB Channel (Unofficial)” (@nusisb), 971 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/nusisb.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.