🏅New collection 💫 🌟Europe size 🌟Ti short 💫model 30/2 🌟size S M L xl xxl WhatsApp number +90 534 760 53 46

Channel
ADO.TR
@ADOerkekelbisecollesiummerter
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,685subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001629017935 |
|---|---|
| Type | Channel |
| Username | @ADOerkekelbisecollesiummerter |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/ADOerkekelbisecollesiummerter |
Topic
Ecommerce storefront — 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 17 September 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 08:36 | 1,685 | +2 |
| 12 Sept 2026, 08:19 | 1,683 | +3 |
| 8 Sept 2026, 14:18 | 1,680 | +3 |
| 31 Aug 2026, 01:44 | 1,677 | +1 |
| 27 Aug 2026, 16:24 | 1,676 | +2 |
| 24 Aug 2026, 14:12 | 1,674 | -6 |
| 20 Aug 2026, 16:48 | 1,680 | -3 |
| 14 Aug 2026, 15:34 | 1,683 | -7 |
| 10 Aug 2026, 20:41 | 1,690 | +1 |
| 7 Aug 2026, 19:40 | 1,689 | no change |
| 7 Aug 2026, 10:16 | 1,689 | first reading |
Engagement
5 posts held, back to 4 August 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 2 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 5 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
🏅New collection 💫 🌟Europe size 🌟Ti short 💫model 30/2 🌟size S M L xl xxl WhatsApp number +90 534 760 53 46
🏅New collection 💫 🌟Europe size 🌟Ti short 💫model 30/2 🌟size S M L xl xxl WhatsApp number +90 534 760 53 46
🏅New collection 💫 🌟Europe size 🌟Ti short 💫model 30/2 🌟size S M L xl xxl WhatsApp number +90 534 760 53 46
🏅New collection 💫 🌟Europe size 🌟Ti short 💫model 30/2 🌟size S M L xl xxl WhatsApp number +90 534 760 53 46
Showing the 5 most recent of 5 posts we hold for @ADOerkekelbisecollesiummerter. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“ADO.TR” (@ADOerkekelbisecollesiummerter), 1,685 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/ADOerkekelbisecollesiummerter.
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.