Sticker, posted without a caption
🤣10

Channel
@tulenvplatie
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
64subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002070656837 |
|---|---|
| Type | Channel |
| Username | @tulenvplatie |
| Description | Живу в своих фантазиях и радуюсь жизни Ссылочка на Фикбук: https://ficbook.net/authors/2815465 Сылочка на Ао3: https://archiveofourown.org/users/Sad_Cloud_25 |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/tulenvplatie |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 10:01 | 64 | no change |
| 13 Aug 2026, 09:48 | 64 | first reading |
17 posts held, back to 13 July 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 12 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 17 (13 July 2026 – 8 August 2026) |
| Views total | 946 |
| Reactions total | 225 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 10:01 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
321 reactions across 16 posts, in 14 distinct kinds. The most used accounts for 18.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5353078917966095610 | 60 | 18.7% | |
| custom 5201786719279523512 | 53 | 16.5% | |
| custom 5355304630148427395 | 40 | 12.5% | |
| custom 5312169908522484281 | 38 | 11.8% | |
| ❤ | 30 | 9.35% | |
| custom 5202048467471441773 | 28 | 8.72% | |
| 🔥 | 25 | 7.79% | |
| 🤣 | 10 | 3.12% | |
| custom 5348233408877189996 | 9 | 2.80% | |
| 👀 | 7 | 2.18% | |
| 💋 | 7 | 2.18% | |
| 🗿 | 7 | 2.18% | |
| 🕊 | 5 | 1.56% | |
| 😨 | 2 | 0.623% |
Custom emoji. 6 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 areTelegram’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 16 of the 17 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 321reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 13 July 2026 to 8 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.
Sticker, posted without a caption
🤣10
Photo, posted without a caption
❤11💋7custom 53530789179660956106
🔵Остров🔵 Персонажи: Люцерис, Лейнор (Джен) Описание: Люцерис помнил дождь, тучи вокруг себя и открывающуюся пасть Вхагар, а дальше лишь непроглядную тьму. Он не помнил, как очутился на берегу. ФИКБУК ТЕЛЕГРАФ Очень короткая зарисовка, но в пост не влезла.
❤7custom 52017867192795235125custom 53530789179660956105
🌟Молоко🌟 Пейринг: Дейрон/Ормунд Метки: флафф, перед сном, пропущенная сцена, родительские чувства, не озвученные романтические чувства, мужская лактация Описание: Ормунд Хайтауэр приходит к Дейрону вечером, чтобы уложить его спать и унять тревогу. ФИКБУК ТЕЛЕГРАФ Не на растишке Дейрон вырос такой двухметровой детиной.
❤12custom 53530789179660956105custom 52020484674714417734🗿3
Мой пупс
custom 52020484674714417739custom 53530789179660956106custom 53553046301484273953
⏪Общий племянник⏩ Пейринг: Деймон/Дейрон/Ормунд Метки: современность, секс втроём, минет, анальный секс, инцест Описание: Таргариена и Хайтауэра смогла объединить лишь одна неожиданная встреча в элитном секс-клубе и их общий племянник. Мы никогда не были так близки, как сейчас. ФИКБУК АО3 ТЕЛЕГРАФ ⏺
custom 53482334088771899969custom 53530789179660956105custom 53553046301484273954
Беременен в 16 Часть 4/6 — Твоя мама приедет завтра. Гвейн заглянул в комнату Дейрона, чтобы пожелать доброго утра. — Я соскучился по ней. — Дейрон выглядел не выспавшимся. — Ты уверен, что не хочешь вернуться вместе с ней домой? Не подумай, что я тебя выгоняю, просто беспокоюсь. — Гвейн прошёл вглубь комнаты и присел на край кровати. — Или ты не хочешь уезжать из-за отца ребенка? Дейрон укутался в одеяло, будт…
custom 53553046301484273959custom 52017867192795235123🕊1
Пятая и шестая часть будут чуть позже, сейчас готовлю черно-зелёный тройничок.
Беременен в 16 Часть 3/4 Положив голову на грудь Ормунда, Дейрон всхлипывал и никак не мог собраться с мыслями, чтобы что-то сказать. Ормунд поглаживал его по спине, но с каждой минутой его терпение заканчивалось. — Ну, перестань, мой хороший. — Я не могу лгать Гвейну, больше не могу, — сквозь слезы выдавил из себя Дейрон. — Разве это считается ложью? Мы скрываем наши отношения, чтобы уберечь его. Ты же не счита…
custom 520178671927952351211custom 53553046301484273953
Беременен в 16 Часть 2/4 Гвейн и Ормунд стояли на кухне, готовили ужин, пока Дейрон делал уроки у себя в комнате. — Надо позвонить Алисенте, — тихо сказал Гвейн. С разговора в кабинете медсестры прошёл день, а Дейрон так и не смог рассказать, кто может быть отцом ребенка. — Я позвоню, скажу, что её сын, которого она нам доверила, соскучился по ней и хочет домой, поэтому мы его возвращаем, а второй ребенок в пода…
custom 535530463014842739510custom 52017867192795235127custom 52020484674714417734
Беременен в 16 Примечание: Дейрон — омега, Гвейн — бета, Ормунд — альфа Часть 1/4 Школьная медсестра вышла из кабинета, оставив Гвейна и Дейрона наедине. — Прости, — сказал Дейрон, опустив голову. — Не извиняйся, просто, как это произошло? Я думал, ты принимаешь подавители. Гвейн взял руки Дейрона в свои, он не хотел, чтобы тот боялся говорить с ним. — Я принимал, но летом сделал перерыв, я не говорил никому. …
custom 53530789179660956109custom 53553046301484273955
Либо я сделаю тебя королем, либо трахну на этом столе.
custom 531216990852248428114👀7custom 52020484674714417737😨2
Showing the 12 most recent of 17 posts we hold for @tulenvplatie. 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.
Citation-graph rank — 1,446,093 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Тюлень в платье🦭” (@tulenvplatie), 64 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/tulenvplatie.
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.