Telegram RegisterThe public register of Telegram
Telegram profile photo for Спиписочек 😛

Channel

Спиписочек 😛

@spisok_dildomena

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2subscribers

+1 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003995878425
TypeChannel
Username@spisok_dildomena
DescriptionБубубу
Created30 July 2026 — measured — dated from the channel’s first post
First recorded18 October 2026
Last confirmed live18 October 2026
Measurements held3
On Telegramt.me/spisok_dildomena

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 18 October 2026 and assigned it the closest of 31 fixed categories, at 91% 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

121.511 August 2026 — 1 subscribers13 October 2026 — 2 subscribers18 October 2026 — 2 subscribers11 August 202618 October 2026
3 measurements spanning 67 days, net +1. 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 1–2 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Oct 2026, 06:222no change
13 Oct 2026, 10:402+1
11 Aug 2026, 21:201first reading

Engagement

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

What this channel posts

Links
5

Lifetime counters from Telegram’s own channel header, read 18 October 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.

Reaction mix

3 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3100.0%

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 2 of the 13 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 30 July 2026 to 23 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

23 Aug 2026, 05:49 UTC234 viewsread 18 October 2026

Небольшое расписание ртшек: Блок 1 1. Рт субботу - воскр с 5 утра и до 5 утра пн 2. Рт всегда 3. Рт всегда 4. Рт по выходным 5. Рт всегда с 23 - 6 утра (мск) 6. Рт всегда с 2-6 утра (мск) ➿➿➿➿➿➿➿ Блок 2 1. Рт в субботу и воскресенье с 10 по 18 (мск) 2. Рт в субботу и воскресенье с 10 по 18 (мск) 3. Рт в воскресенье с 10 по 6 (пн) (мск) 4. Рт всегда /ваши рт посты всегда идет в отложку, если рт не "сейчас", поэтому…

15 Aug 2026, 19:28 UTC252 viewsread 18 October 2026

❌здесь можно предложить вп ❌❌❌всему списку: (учитывайте порог, иначе не ртшну.)

11 Aug 2026, 18:52 UTC261 viewsread 18 October 2026

+ у меня разница с мск 5 часов, так что если я не ответил сразу, значит сплю...

11 Aug 2026, 04:09 UTC285 views3 reactionsread 18 October 2026

Для быстрого разбора: (пдп) [порог] Блок 1 1. (55+) [0+] дни база | рт пост 2. (90+) [0+] дни база + хейт чего угодно | рт пост 3. (90+) [0+ блоги, рб. 5+ ост] дни | рт пост 4. (85+) [0+] дни база | рт пост 5. (65+) [0+ для схожих тем, 25+ ост] дни база | рт пост 6. (5+) [0+] дни база | рт пост Блок 2 1. (330+) [0+ РБ 75+ ост] дни база | рт пост 2. (150+) [0+ любой контент по билдермену, рб плейсы 10+, ост 25+] д…

👍3

11 Aug 2026, 04:07 UTC280 viewsread 18 October 2026

Блок 2 (пдп) [порог] (От 100 до 500 пдп) 1.@roblox_st1ckers (350+) [0+ для рб, ост 115+] рт пост ~ вп пост Канал по стикерам роблокса; дни выходные; dni база 2.@blog_devid_bazuki (150+) [0+ биллермен; рб плейсы 10+; ост 25+] рт пост ~ вп пост Роблокс блог; дни вп суббота, воскресенье; dni: "-филия", издевательство над животыми. 3.@amarahBlog (220+) [0+ все] рт пост ~ вп пост Роблокс блог; дни воскресенье; dni: х…

11 Aug 2026, 04:04 UTC262 views0 reactionsread 18 October 2026

Блок 1 (пдп) [порог] (От 0 до 100 пдп) 1. @nomaleT_blog (55+) [0+] рт пост ~ вп пост Блог по роблоксу ; рт в субботу, воскресенье ; дни база. 2.@SHEDLETSKYblogBLaMe (90+) [0+] рт пост ~ вп пост Блог по роблоксу ; dni база + хейт чего угодно ; дни - суббота 3.@Divine_pumpkin (90+) [0+ блоги, рб/5+ ост] рт пост ~ вп пост Блог по роблоксу ; dni ; дни - всегда. 4. @BUILDERMAN_CF (85+)[0+ контент билд, 5+ РБ и ост]…

30 Jul 2026, 14:24 UTC336 viewsread 18 October 2026

Анкета на впшера: пока нанять нельзя 1. Пиано/пианино (комбо эмодзи 🛠) 2. Часовой пояс +5 мск 3. Делаю вп примерно 5 в неделю 4. dni: моя база + каналы, где вп/рт/навигация/название написаны непонятным шрифтом. 5. Кол-во подписчиков не важно. (Юз: @pionin0 (написать невозможно, соо за звезды))

30 Jul 2026, 14:17 UTC305 viewsread 18 October 2026

Ой-ей, Здравствуйте, тута список с впшками

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

Mentions

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.

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

“Спиписочек 😛” (@spisok_dildomena), 2 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/spisok_dildomena.

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.