Telegram RegisterThe public register of Telegram
Telegram profile photo for Dewtee gap archive

Channel

Dewtee gap archive

@dewteesarchive

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

8subscribers

+2 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-1003996505449
TypeChannel
Username@dewteesarchive
CreatedBetween 1 April 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live19 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/dewteesarchive

Growth

697.514 August 2026 — 6 subscribers14 August 2026 — 6 subscribers23 August 2026 — 8 subscribers10 September 2026 — 9 subscribers19 September 2026 — 8 subscribers814 August 202619 September 2026
5 measurements spanning 35 days, net +2. 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 6–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 04:408-1
10 Sept 2026, 02:589+1
23 Aug 2026, 10:368+2
14 Aug 2026, 19:186no change
14 Aug 2026, 19:046first reading

Engagement

20 posts held, back to 5 August 2026the 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 20 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

5 Aug 2026, 04:09 UTC2 viewsread 14 August 2026
Forwarded from @iRoChatBot

https://t.me/dewteechamomile/2425 چرا هیت؟

5 Aug 2026, 04:09 UTC3 viewsread 14 August 2026
Forwarded from @dewteechamomile

ارهههه😭😭😭🥺🥺🥺

5 Aug 2026, 04:09 UTC2 viewsread 14 August 2026
Forwarded from @dewteechamomile

خیلی اونم با استعداد دیو تو کشیدن خیلی گوگولی میشه هر چند دیدیم ترکیب دیوتی تو نقاشی چطوریاست😂🤣 بیا دعا کنیم یدونه باشه وگرنه هیت میخورن بچهام 😭😭😭 بعد من نمیتونم دوتا بچه رو باهم هندل کنم

5 Aug 2026, 04:09 UTC2 viewsread 14 August 2026
Forwarded from @iRoChatBot

https://t.me/dewteechamomile/2425 بچه تی قطعا شکل و شمایل خرگوش رو داره🥹

5 Aug 2026, 04:09 UTC2 viewsread 14 August 2026
Forwarded from @iRoChatBot

اگه ۲۰۲۷ سریال داشته باشیم که امضای کاپل ثابت شدنشون باشه بنده جمعووو شییریینیییی میدمم فکر کنین نینی‌شونو دیو طراحی کنه، معلومه که میشه خوشگل‌ترین😭😭اوه نوووووو

5 Aug 2026, 04:09 UTC3 viewsread 14 August 2026
Forwarded from @iRoChatBot

https://t.me/dewteechamomile/2417 توروخدا نه😭🫠 من خیلی دوسشون دارم خیلی کنار هم قشنگن😭 اونا از اینکه باهمن خوشحالن ایشالا چندین سال قراره سریالای خوشگل بدن بهمون😌

5 Aug 2026, 04:09 UTC2 viewsread 14 August 2026
Forwarded from @iRoChatBot

https://t.me/dewteechamomile/2420 دیو هفته پیش به فنا گفت به این زودیا منتظر نباشید🫠

5 Aug 2026, 04:09 UTC4 viewsread 14 August 2026
Forwarded from @dewteechamomile

میگن وقتی یدونه ماسکت میتونید داشته باشید چرا دوتا کلا اوایل یکم مخالفت و نظرات منفی همراهش هست

5 Aug 2026, 04:09 UTC4 viewsread 14 August 2026
Forwarded from @dewteechamomile

انشالله که داریم اگه بخواد یدونه باشه هردو باید طراحی کنن

5 Aug 2026, 04:09 UTC4 viewsread 14 August 2026
Forwarded from @dewteechamomile

ببینید الان چیزی مشخص نیست بعد اتمام سریال باس ببینیم total ترند چقدر میشه اونموقع است که جمم تصمیم میگیره اونا رو نگه داره یا نه هر چی باشه من عاشقشونم چه کاپل چه نه

5 Aug 2026, 04:09 UTC4 viewsread 14 August 2026
Forwarded from @dewteechamomile

دیو اولین بارش نیست اینو میگه ولی خوب میدونم اونا هم مثل ما منتظر این لحظه ان که بچه اشون رو بهمون نشون بدن

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

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.

Mentions

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

“Dewtee gap archive” (@dewteesarchive), 8 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/dewteesarchive.

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.