Telegram RegisterThe public register of Telegram
Telegram profile photo for usernameshop portal

Channel

usernameshop portal

@usernameshop

On this record: Topic · Growth · Engagement · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

46subscribers

-7,912 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002489038473
TypeChannel
Username@usernameshop
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live5 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/usernameshop

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 the other topics.

Growth

225,19712,599.56 August 2026 — 7,958 subscribers7 August 2026 — 7,960 subscribers9 August 2026 — 7,968 subscribers12 August 2026 — 7,994 subscribers15 August 2026 — 8,017 subscribers19 August 2026 — 8,032 subscribers22 August 2026 — 8,058 subscribers25 August 2026 — 8,073 subscribers28 August 2026 — 8,089 subscribers31 August 2026 — 8,104 subscribers3 September 2026 — 8,130 subscribers8 September 2026 — 8,155 subscribers13 September 2026 — 8,167 subscribers17 September 2026 — 8,186 subscribers26 September 2026 — 8,229 subscribers5 October 2026 — 25,197 subscribers9 October 2026 — 25,103 subscribers13 October 2026 — 25,136 subscribers14 October 2026 — 25,139 subscribers16 October 2026 — 25,151 subscribers17 October 2026 — 25,154 subscribers18 October 2026 — 25,148 subscribers19 October 2026 — 25,151 subscribers21 October 2026 — 24,968 subscribers22 October 2026 — 2 subscribers29 October 2026 — 17 subscribers5 November 2026 — 46 subscribers466 August 20265 November 2026
27 measurements spanning 91 days, net -7,912. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
5 Nov 2026, 00:4146+29
29 Oct 2026, 06:4417+15
22 Oct 2026, 09:282-24,966
21 Oct 2026, 05:1124,968-183
19 Oct 2026, 05:2725,151+3
18 Oct 2026, 03:4725,148-6
17 Oct 2026, 04:2825,154+3
16 Oct 2026, 01:1625,151+12
14 Oct 2026, 23:4925,139+3
13 Oct 2026, 16:0125,136+33
9 Oct 2026, 16:5625,103-94
5 Oct 2026, 06:3725,197+16,968
26 Sept 2026, 09:198,229+43
17 Sept 2026, 13:208,186+19
13 Sept 2026, 03:378,167+12
8 Sept 2026, 19:028,155+25
3 Sept 2026, 07:068,130+26
31 Aug 2026, 03:478,104+15
28 Aug 2026, 10:248,089+16
25 Aug 2026, 09:548,073first reading

Engagement

261 posts held, back to 29 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 53 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1000.3%
avg views ÷ 46 subscribers
Avg views / post
460
113 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
113
of 261 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 21 October 2026
Posts held261 (29 July 2026 – 21 October 2026)
Views total51,995
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Oct 2026, 00:34 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

Telegram’s own ‘edited’ marker: 8 of 113 posts held from the last 30 days (7.08%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

21 Oct 2026, 03:26 UTC381 viewsread 22 October 2026

NEW CRYPTO FINAL 4L TELEGRAM PAIR ✈️ @txid + @bc1q BIN: 200k C/O: 150k ✈️ @Plug for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

21 Oct 2026, 00:32 UTC415 viewsread 22 October 2026

NEW TELEGRAM ✈️ @murdering BIN: Taking Offers C/O: 4k ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

20 Oct 2026, 21:27 UTC450 viewsread 22 October 2026

NEW TELEGRAM ✈️ @cucked BIN: 10k C/O: ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

20 Oct 2026, 20:09 UTC438 viewsread 22 October 2026

NEW TELEGRAM ✈️ @disappointed BIN: 5k C/O: 2k ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

20 Oct 2026, 00:16 UTC629 viewsread 22 October 2026

NEW TELEGRAM BUNDLE ✈️ @yhwach + @starrk BIN: Taking Offers C/O: ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

19 Oct 2026, 22:29 UTC615 viewsread 22 October 2026

NEW TELEGRAM ✈️ @skimask BIN: Taking Offers C/O: ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

19 Oct 2026, 08:15 UTC640 viewsread 22 October 2026

NEW TELEGRAM ✈️ @dentist BIN: 15k C/O: ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

19 Oct 2026, 01:29 UTC622 viewsread 22 October 2026

NEW MC 🌐 Devious BIN: Taking Offers C/O: 2.5k ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

19 Oct 2026, 00:29 UTC595 viewsread 22 October 2026

NEW MC 🌐 not BIN: Taking Offers C/O: 7k ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

18 Oct 2026, 23:25 UTC551 viewsread 22 October 2026

NEW TELEGRAM ✈️ @disrupt BIN: 7.5k C/O: ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

18 Oct 2026, 22:55 UTC534 viewsread 22 October 2026

NEW TELEGRAM ✈️ @flamingo BIN: 5k C/O: 3k ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

18 Oct 2026, 20:48 UTC527 viewsread 22 October 2026

NEW TELEGRAM ✈️ @strive BIN: Taking Offers C/O: 3.8k ✈️ @Obey for contact 🤝 @MMing 💧 Rainbet.com the #1 Non-KYC Crypto Casino & Sportsbook @rainbetcom

Showing the 12 most recent of 261 posts we hold for @usernameshop. 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.

Posts edited after publishing

@usernameshop edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
18 August 2026
Most recent edit
11 October 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @usernameshop as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
13 October 2026
Median time before seen missing
47 hours
Seen missing in the last 30 days
2

Mentions

Named by 10 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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

“usernameshop portal” (@usernameshop), 46 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/usernameshop.

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.