Telegram RegisterThe public register of Telegram
Telegram profile photo for Protection Escrow

Channel

Protection Escrow

@protection

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

6,334subscribers

+6,252 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003151643512
TypeChannel
Username@protection
Created14 October 2025measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live13 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/protection

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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

826,7343,4086 August 2026 — 82 subscribers9 August 2026 — 82 subscribers15 August 2026 — 86 subscribers22 August 2026 — 5,813 subscribers25 August 2026 — 5,865 subscribers28 August 2026 — 5,326 subscribers31 August 2026 — 6,734 subscribers3 September 2026 — 5,714 subscribers8 September 2026 — 6,324 subscribers13 September 2026 — 6,334 subscribers6,3346 August 202613 September 2026
10 measurements spanning 38 days, net +6,252. 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
13 Sept 2026, 00:386,334+10
8 Sept 2026, 20:386,324+610
3 Sept 2026, 21:415,714-1,020
31 Aug 2026, 21:136,734+1,408
28 Aug 2026, 10:445,326-539
25 Aug 2026, 04:485,865+52
22 Aug 2026, 09:175,813+5,727
15 Aug 2026, 14:5686+4
9 Aug 2026, 18:0182no change
6 Aug 2026, 03:5082first reading

Engagement

4 posts held, back to 14 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 4 posts for this entry, the most recent from 18 February 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

18 Feb 2026, 03:00 UTC≈1,570 viewsread 9 August 2026

Boo’s MM Service 🤍 Fee: $5 fixed ✈️ t.me/bunny7262 ✅ t.me/boovouches 🤝 oguser.com/bunny

17 Feb 2026, 00:50 UTC≈2,120 viewsread 9 August 2026
Photo

Introducing @Protection Escrow Services. Your trusted middleman service for secure and smooth transactions. We handle each deal professionally, ensuring your assets or accounts are safe until all agreed conditions are met. Our service fee is fixed at $5 per transaction. Work with us and experience the confidence that comes from having a reliable, neutral intermediary on your side. By using our services, you ackno

Showing the 4 most recent of 4 posts we hold for @protection. 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 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Protection Escrow” (@protection), 6,334 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/protection.

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.