Telegram RegisterThe public register of Telegram
Telegram profile photo for Doctor vouch

Channel

Doctor vouch

@scanshops

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

512subscribers

-7,405 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1003362646937
TypeChannel
Username@scanshops
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live12 October 2026
Measurements held12
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/scanshops

Topic

Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

5127,9174,214.514 August 2026 — 7,917 subscribers15 August 2026 — 7,915 subscribers17 August 2026 — 7,913 subscribers20 August 2026 — 7,911 subscribers23 August 2026 — 7,907 subscribers26 August 2026 — 7,900 subscribers1 September 2026 — 7,895 subscribers5 September 2026 — 3,929 subscribers10 September 2026 — 532 subscribers18 September 2026 — 523 subscribers3 October 2026 — 513 subscribers12 October 2026 — 512 subscribers14 August 202612 October 2026
12 measurements spanning 60 days, net -7,405. 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
Measured (UTC)SubscribersChange
12 Oct 2026, 16:06512-1
3 Oct 2026, 00:16513-10
18 Sept 2026, 18:01523-9
10 Sept 2026, 22:00532-3,397
5 Sept 2026, 22:183,929-3,966
1 Sept 2026, 23:457,895-5
26 Aug 2026, 22:287,900-7
23 Aug 2026, 12:587,907-4
20 Aug 2026, 08:277,911-2
17 Aug 2026, 18:457,913-2
15 Aug 2026, 00:067,915-2
14 Aug 2026, 02:467,917first reading

Engagement

22 posts held, back to 17 June 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 9 pages of 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 22 posts for this entry, the most recent from 26 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

26 Aug 2026, 01:52 UTC≈1,020 viewsread 28 August 2026

Very sorry for the delay, buddy. Your document worked. Thanks so much.

15 Aug 2026, 20:22 UTC≈2,000 viewsread 28 August 2026

@drdocuments drew the DL and State BA. The quality is excellent. The service is top-notch! The app works great (at first I thought I was talking to a bot 😅 Thank you, +1 to my list of artists!

11 Aug 2026, 10:26 UTC≈3,010 viewsread 28 August 2026

I think you are fast and good. We can do long term business

11 Aug 2026, 10:26 UTC≈3,010 viewsread 28 August 2026

Hey Everything went well. So I will add you with one of my team member. He requires some doc works

8 Aug 2026, 17:35 UTC≈3,860 viewsread 28 August 2026

@drdocuments The only one who helped while everyone else was busy for various reasons. I urgently needed to print a state sheet using my template. He did everything quickly and beautifully. My account was canceled, and my money was withdrawn. Thanks to the service

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

Mentions

Named by 6 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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“Doctor vouch” (@scanshops), 512 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/scanshops.

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.