Telegram RegisterThe public register of Telegram
Telegram profile photo for Лудольф

Channel

Лудольф

@Ludolfer

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

1,360subscribers

+762 since we began measuring on 27 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001877941650
TypeChannel
Username@Ludolfer
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live13 November 2026
Measurements held9
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/Ludolfer

Topic

Hacking & security — 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 13 October 2026 and assigned it the closest of 31 fixed categories, at 36% 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 the other topics.

Growth

5981,36097927 September 2026 — 598 subscribers27 September 2026 — 598 subscribers4 October 2026 — 669 subscribers13 October 2026 — 718 subscribers21 October 2026 — 882 subscribers29 October 2026 — 988 subscribers5 November 2026 — 1,197 subscribers8 November 2026 — 1,257 subscribers13 November 2026 — 1,360 subscribers27 September 202613 November 2026
9 measurements spanning 48 days, net +762. 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 484–1,474 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 16:061,360+103
8 Nov 2026, 16:461,257+60
5 Nov 2026, 06:001,197+209
29 Oct 2026, 11:21988+106
21 Oct 2026, 13:01882+164
13 Oct 2026, 18:41718+49
4 Oct 2026, 14:16669+71
27 Sept 2026, 01:22598no change
27 Sept 2026, 00:47598first reading

Engagement

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

What this channel posts

Video runtime
5m 27s
Average length
36s

Measured directly from 9 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

223 reactions across 18 posts, in 13 distinct kinds. The most used accounts for 44.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁9944.4%
🤣9140.8%
😱125.38%
😐52.24%
👎41.79%
😨31.35%
👏20.897%
🤔20.897%
❤10.448%
👍10.448%
💊10.448%
🔥10.448%
😈10.448%

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

Measured over the 18 most recent posts we hold, published 24 September 2026 to 26 September 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

26 Sept 2026, 15:31 UTC283 views9 reactionsread 27 September 2026
Video

. Лудольф. Подписаться

😁9

26 Sept 2026, 12:20 UTC357 views4 reactionsread 27 September 2026
Photo

Криптоплатформу Duelbits для прогнозов обнесли на 7 миллионов $ Хакер в два захода вытащил круглую сумму и раскидал по кошелькам. Известно, что подобный случай с данной компанией был пару лет назад, тогда злоумышленники обогатились на 4,6 млн долларов. Пора открывать линию прогнозов на то, когда Duelbits ограбят в следующий раз. Лудольф. Подписаться

🤣4

26 Sept 2026, 10:20 UTC460 views7 reactionsread 27 September 2026
Photo

Когда уволился со стройки и депнул в казик Лудольф. Подписаться

😁7

26 Sept 2026, 09:15 UTC433 views9 reactionsread 27 September 2026
Video

Раз раз раз это хардбасс Лудольф. Подписаться

🤣8👎1

26 Sept 2026, 08:50 UTC446 views12 reactionsread 27 September 2026
Video

Обычные лакомства казино стримеров Лудольф. Подписаться

🤣7😐4👎1

25 Sept 2026, 21:29 UTC≈1,080 views13 reactionsread 27 September 2026
Video

Тем временем мемы в тиктоках... Лудольф. Подписаться

🤣12💊1

25 Sept 2026, 21:19 UTC687 views24 reactionsread 27 September 2026
Video

Гиалуроновый минотавр пробивает тройку на 70к Лудольф. Подписаться

😁13🤣11

25 Sept 2026, 20:32 UTC≈4,910 views39 reactionsread 27 September 2026
Video

Пятничной ДВИЖУХИ вам в ленту Лудольф. Подписаться

😁30🤣8👏1

25 Sept 2026, 18:41 UTC798 views6 reactionsread 27 September 2026
Photo

В правительстве РФ заявили о необходимости доработки законопроекта о запрете рекламы нелегальных азартных игр. Лудольф. Подписаться

😁6

25 Sept 2026, 16:40 UTC717 views3 reactionsread 27 September 2026
Photo

ЦБ будет следить за НАЛИЧКОЙ у Россиян Представители власти хотят знать источник наличных денег у россиян при пополнении счетов. Будут проверяться внесение рублей и обмен валюты у физлиц и юрлиц. Регулятор также готовит поправки в 115-ФЗ, чтобы усилить контроль за источниками наличных. После ужесточения законов, регулирующих безналичные операции, оборот наличных средств вырос на 2,5 триллиона рублей, в частности и…

😨3

25 Sept 2026, 13:55 UTC687 views11 reactionsread 27 September 2026
Video

Пацан снял видео, где рассказывает что украсть 50 лямов рублей очень выгодно Для каких хомячков это снято? Как он ворованные бабки собрался в банке на вклад ложить? Где вообще 50кк украсть можно, есть мысли? Лудольф. Подписаться

🤣11

25 Sept 2026, 11:53 UTC730 views13 reactionsread 27 September 2026
Photo

❗️🇧🇷 Сегодня президент Бразилии намерен объявить о полном запрете ставок и онлайн-казино в стране. Лудольф. Подписаться

😱12👏1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“Лудольф” (@Ludolfer), 1,360 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/Ludolfer.

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.