Telegram RegisterThe public register of Telegram
Telegram profile photo for DED OMLETTE

Channel

DED OMLETTE

@dedomlette

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

299subscribers

+45 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-1002180309855
TypeChannel
Username@dedomlette
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/dedomlette

Growth

254299276.56 August 2026 — 254 subscribers7 August 2026 — 254 subscribers14 August 2026 — 258 subscribers21 August 2026 — 265 subscribers28 August 2026 — 293 subscribers5 September 2026 — 299 subscribers6 August 20265 September 2026
6 measurements spanning 30 days, net +45. 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 247–306 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 14:21299+6
28 Aug 2026, 11:24293+28
21 Aug 2026, 00:52265+7
14 Aug 2026, 18:13258+4
7 Aug 2026, 02:03254no change
6 Aug 2026, 21:02254first reading

Engagement

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

Reaction mix

347 reactions across 8 posts, in 11 distinct kinds. The most used accounts for 40.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
14240.9%
🔥11934.3%
custom 5237798125975912505236.63%
custom 5463345893983926454216.05%
custom 5271981538756541108123.46%
custom 5465519392248838285123.46%
custom 5271542953876142980102.88%
custom 523807490655336940130.865%
custom 533715492298923784430.865%
custom 527188031926227812610.288%
custom 527404512880834823710.288%

Custom emoji. 9 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 8 of the 8 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 347 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 24 June 2026 to 2 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

2 Aug 2026, 12:52 UTC103 views67 reactionsread 7 August 2026
Photo

Скетчи на мусорной бумаге #tf2fanart #sketchbook

🔥3218custom 527154295387614298010custom 52719815387565411087

24 Jul 2026, 09:13 UTC≈1,910 views49 reactionsread 7 August 2026
Photo

Сегодня у меня день рождения! 🐬 За этот год стала делать много интересных штук по анимации и артам, которые приносят радость. Спасибо, что продолжаете следите за моим творчеством. Вы очень приятная аудитория! Буду очень благодарна, если сделаете подарок в виде репоста🌸

34🔥13custom 52380749065533694012

16 Jul 2026, 18:16 UTC290 views26 reactionsread 7 August 2026
Video

Сделала маленький ролик с разных ракурсов для представления локации. Представление как бы могло открываться начало комикса Разбиралась как работает камера. Меня не всё устраивает в этой локации, но это первый вообще опыт, все равно его люблю. Хотелось вкусненько представить Ссылка на Ютуб версию #tf2fanart #3Danimation@dedomlette

custom 5463345893983926454138🔥5

10 Jul 2026, 12:46 UTC332 views46 reactionsread 7 August 2026
Photo

Моделировала лоу поли копию фрейма из Хэллоуиновского выпуска комикса ТФ2 Оригинал в комментах #tf2fanart #3Danimation@dedomlette

🔥268custom 54633458939839264547custom 52719815387565411083custom 52380749065533694011custom 52718803192622781261

28 Jun 2026, 07:11 UTC422 views65 reactionsread 7 August 2026
Photo

Ностальджи фото 5/6 #tf2fanart#art@dedomlette

37custom 523779812597591250514custom 546551939224883828510custom 53371549229892378443custom 52740451288083482371

25 Jun 2026, 15:31 UTC367 views19 reactionsread 7 August 2026

https://youtu.be/R_WUR7ljpF8?si=q4rfHWr2I-WYLBcF Выложила на ютуб обзор скетчбуков, если кому-то там удобнее глянуть

13🔥6

24 Jun 2026, 13:55 UTC341 views43 reactionsread 7 August 2026
Photo

Ну и еще скоро узнаете зачем делала ностальгические фотки #3Danimation@dedomlette #tf2fanart

🔥29custom 523779812597591250593custom 52719815387565411082

24 Jun 2026, 10:08 UTC305 views32 reactionsread 7 August 2026
Photo

Немного начну выкладывать работы по 3д моделированию. Первый опыт в скульптинге Мой гига ребенок 😭 Очень его люблю и весь крышесносный процесс создания Попозже сделаю видосик с переодевашками, у него вся одежда съемная)) Я не фурри наверное #3Danimation@dedomlette

21🔥8custom 54655193922488382852custom 54633458939839264541

Showing the 8 most recent of 8 posts we hold for @dedomlette. 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.

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

“DED OMLETTE” (@dedomlette), 299 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/dedomlette.

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.