Telegram RegisterThe public register of Telegram
Telegram profile photo for SHIPPERING

Bot

SHIPPERING

@SHIPPERINGbot

On this record: Topic · Growth · Engagement · Citations · Cite this entry

144,902monthly users

-4,988 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID674931693
TypeBot
Username@SHIPPERINGbot
First recorded9 August 2026
Last confirmed live30 August 2026
Measurements held17
Confirmed unchanged2 times, most recently 30 August 2026
On Telegramt.me/SHIPPERINGbot

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

143,999149,890146,944.57 August 2026 — 149,890 monthly users9 August 2026 — 149,890 monthly users10 August 2026 — 148,680 monthly users11 August 2026 — 148,090 monthly users12 August 2026 — 147,503 monthly users14 August 2026 — 146,295 monthly users15 August 2026 — 145,607 monthly users16 August 2026 — 144,692 monthly users17 August 2026 — 144,912 monthly users19 August 2026 — 144,797 monthly users20 August 2026 — 144,707 monthly users22 August 2026 — 143,999 monthly users24 August 2026 — 144,329 monthly users25 August 2026 — 144,707 monthly users26 August 2026 — 145,344 monthly users28 August 2026 — 145,424 monthly users29 August 2026 — 144,902 monthly users144,9027 August 202629 August 2026
17 measurements spanning 21 days, net -4,988. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 143,115–150,774 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
29 Aug 2026, 10:16144,902-522
28 Aug 2026, 12:28145,424+80
26 Aug 2026, 10:02145,344+637
25 Aug 2026, 07:45144,707+378
24 Aug 2026, 08:18144,329+330
22 Aug 2026, 13:14143,999-708
20 Aug 2026, 02:42144,707-90
19 Aug 2026, 01:52144,797-115
17 Aug 2026, 22:38144,912+220
16 Aug 2026, 22:03144,692-915
15 Aug 2026, 17:57145,607-688
14 Aug 2026, 07:33146,295-1,208
12 Aug 2026, 04:42147,503-587
11 Aug 2026, 01:42148,090-590
10 Aug 2026, 01:06148,680-1,210
9 Aug 2026, 15:02149,890no change
7 Aug 2026, 23:29149,890first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Forward network

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.

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 29 August 2026 — this entry's latest reading, not the date you are reading this.

“SHIPPERING” (@SHIPPERINGbot), 144,902 monthly users as measured 29 August 2026. Telegram Register, tgregister.com/channel/SHIPPERINGbot.

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.