Channel
@dungeon_princess
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
205subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002328699119 |
|---|---|
| Type | Channel |
| Username | @dungeon_princess |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 14 September 2026 |
| On Telegram | t.me/dungeon_princess |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 16:17 | 205 | +1 |
| 28 Aug 2026, 08:25 | 204 | +2 |
| 22 Aug 2026, 02:37 | 202 | -1 |
| 14 Aug 2026, 16:05 | 203 | -3 |
| 7 Aug 2026, 03:48 | 206 | no change |
| 6 Aug 2026, 15:36 | 206 | first reading |
7 posts held, back to 11 January 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 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 7 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
273 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 23.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5359372775926547678 | 64 | 23.4% | |
| custom 5235462385321388485 | 55 | 20.1% | |
| custom 5363869366167285529 | 46 | 16.8% | |
| custom 5361748017395283734 | 34 | 12.5% | |
| custom 5361797065921806009 | 31 | 11.4% | |
| custom 5363847461834077186 | 16 | 5.86% | |
| custom 5361882269483023343 | 14 | 5.13% | |
| custom 5355167234144610638 | 13 | 4.76% |
Custom emoji. Every row above is a 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 7 of the 7 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 273 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 11 January 2026 to 5 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.
✧ 2/50 была опробована новая система – 10 свечей. самой большой сложностью в проведении было удерживать атмосферу ужаса, зато персонажи у моих игроков вышли очень живыми! опыт, который точно скоро повторим.
custom 535937277592654767817custom 53617970659218060093custom 53618822694830233432custom 53617480173952837341custom 53638474618340771861
✧ 1/50 поставила напоминание, чтобы постить. это оказывается сложнее, чем я думала: в ожиданиях идеальной картинки, времени для съемки, более красивой укладки можно потерять маленькие, но чудесные моменты. первым таким моментом будет кофе, без которого я не вижу ни одно утро🍵🍽
custom 536179706592180600919custom 523546238532138848510custom 53638474618340771867custom 53551672341446106382custom 53593727759265476782
✧ ожидается ребрендинг. что-то пугающее и, надеюсь, впечатляющее. собираюсь вернуть себе себя и делиться всем. начнем с вызова, за который берусь без уверенности, но со смелостью утопающего: постить что-то 50 дней подряд! 0/50 – сладкий котенок для вас😑
custom 535937277592654767823custom 536386936616728552914custom 53617480173952837347custom 53618822694830233434custom 53638474618340771861
✧ вспомнить, как ходить на фестивали: done⭐️
custom 523546238532138848534custom 535937277592654767821custom 536386936616728552917custom 53617480173952837342custom 53618822694830233432custom 53638474618340771861
✧ пока что канал пустует, у автора тяжелый период – но скоро обязательно оживет! расскажите, как ваши дела?😳
custom 536174801739528373421custom 53551672341446106388custom 53638693661672855298custom 52354623853213884852custom 53638474618340771861
✧ 2025, часть 2 пусть новый год принесет больше вдохновения, романтизации мелочей, поиска себя в новом и уверенности в любом деле, которым доведется заняться🌹🩹
custom 53617970659218060098custom 53638693661672855297custom 53617480173952837343custom 53618822694830233432custom 52354623853213884851custom 53551672341446106381
✧ 2025, часть 1 прошедший год был тяжелым и темным. но и в нем были яркие моменты: игротеки, мероприятия, настольный челлендж, организация фотосетов и вечеринок, пара отыгранных кампейнов и пробы себя в новых ролях и образах😜😞
custom 52354623853213884858custom 53638474618340771865custom 53618822694830233434custom 53551672341446106382custom 53593727759265476781custom 53617970659218060091
Showing the 7 most recent of 7 posts we hold for @dungeon_princess. 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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“dungeon princess ✧” (@dungeon_princess), 205 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/dungeon_princess.
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.