Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐃𝐚𝐫𝐤 𝐒𝐩𝐚𝐫𝐤 𝐈𝐧𝐟𝐨

Channel

𝐃𝐚𝐫𝐤 𝐒𝐩𝐚𝐫𝐤 𝐈𝐧𝐟𝐨

@dark_spark_kf

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

408subscribers

-6 since we began measuring on 3 September 2026

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

Register entry

Telegram ID-1003377089500
TypeChannel
Username@dark_spark_kf
CreatedBetween 1 November 2025 and 4 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 September 2026
Last confirmed live26 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/dark_spark_kf

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

408435421.53 September 2026 — 414 subscribers3 September 2026 — 414 subscribers5 September 2026 — 435 subscribers26 September 2026 — 408 subscribers3 September 202626 September 2026
4 measurements spanning 23 days, net -6. 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 404–439 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 20:37408-27
5 Sept 2026, 13:37435+21
3 Sept 2026, 17:22414no change
3 Sept 2026, 16:47414first reading

Engagement

20 posts held, back to 4 March 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.

ERR · 30 days
25.5%
avg views ÷ 408 subscribers
Avg views / post
104
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 August 2026
Posts held20 (4 March 2026 – 29 August 2026)
Views total104
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 17:22 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.

Reaction mix

47 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 23.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52606231283750957131123.4%
💋714.9%
custom 5260335812242863731612.8%
custom 5363823667715271591612.8%
custom 5323323569223001338510.6%
custom 5361766764927552849510.6%
custom 533905907956007008848.51%
custom 533954164490557874736.38%

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

Measured over the 20 most recent posts we hold, published 4 March 2026 to 29 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.

Telegram Stars

Stars received
13
across the posts below
Posts paid on
4
of 20 we hold a reading for · 20%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @dark_spark_kf. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 4 March 2026 to 29 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

29 Aug 2026, 19:40 UTC104 viewsread 3 September 2026

напишите свои претензии или предложения по поводу кф

13 Aug 2026, 19:23 UTC463 views9 reactionsread 3 September 2026
Photo

Дорогие участники и нью кф. Я уже не раз сталкиваюсь с такой ситуацией, когда вы перекидываете ссылку на чат своим знакомым. Поэтому я в первый и последний раз говорю: ссылку на чат кидаю я лично. Если ваши знакомые хотят к нам, пусть напишут мне, ну или я сам им напишу. Я не кусаюсь.

custom 52606231283750957136custom 53233235692230013382custom 53390590795600700881

11 Aug 2026, 21:52 UTC545 views8 reactionsread 3 September 2026

Дорогие будущие нью, я повторяю вам: мы не собираемся высасывать из вас актив. Мы можем помочь влиться при вашем сотрудничестве, но высасывать из вас слова мы не должны.

custom 53638236677152715914custom 52603358122428637312custom 53233235692230013382

7 Aug 2026, 19:38 UTC532 views2 reactionsread 3 September 2026
Photo

мы создали анонимный бот кф @dark_spark_anonbot вы можете написать туда что хотите не считая бесполезных вещей таких как спам, если хотите можете вообще выговориться или сказать кто вам нравится из кф или свое мнение о чем то короче говоря чо хотите, если будете спамить то бот вам выдаст бан

custom 52606231283750957132

7 Aug 2026, 12:33 UTC340 views2 reactionsread 3 September 2026
Photo

здравствуйте на связи влд по поводу ассоциаций, я часто замечаю что в них хотят участвовать люди не состоящие в нашем кф, поэтому хочу вас предупредить: в ассоциациях могут участвовать только участники кф поэтому вступайте к нам)

custom 53617667649275528492

6 Aug 2026, 11:28 UTC308 viewsread 3 September 2026

Если что, набор у нас все еще открыт. Куда писать для вступления — написано в закрепе.

Signed 𝐃𝐈𝐀𝐌’𝐕

23 Jul 2026, 04:19 UTC607 views11 reactionsread 3 September 2026

Организаторы конференции Dark Spark обращаются к участникам с просьбой проявлять активность или выходить из конференции самостоятельно. мы не должны искать причин молчания и просить в личных сообщениях. Администрация не намерена разбираться с оправданиями или просьбами от знакомых.

custom 53390590795600700883custom 52603358122428637312custom 53617667649275528492custom 52606231283750957131custom 53233235692230013381custom 53395416449055787471custom 53638236677152715911

Signed 𝐃𝐈𝐀𝐌’𝐕

16 Jul 2026, 14:17 UTC665 views2 reactionsread 3 September 2026
Photo

🤩🤩🤩🤩 🤩🤩🤩🤩🤩✨ 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 мы ищем ответственных администраторов вы нам подходите если : • вы хорошо выполняете свою работу • ответственный человек • умеете разговаривать с людьми своим админам мы платим за их труд , чем лучше ваша работа тем больше у вас прав и доверия ( возможно даже зарплата ) мы не собираемся брать тех кто хочет просто иметь статус администратора и при этом получать за это …

custom 52603358122428637312

Signed 𝐃𝐢𝐚𝐦

12 Jul 2026, 13:49 UTC445 views2 reactionsread 3 September 2026
Photo

⭐️ 🤩🤩🤩🤩 🤍🤍🤍🤍🤍🤍🤍🤍 правила 🤍🤍🤍🤍🤍🤍🤍 Ведущий подберет ассоциации на тему автомобильных марок, соответствующие вашему профилю. Для участия необходимо оставить «+» в комментариях, участвовать могут только 20 человек начало игры в 20:00 по мск времени ведущий : @whixxd 🤍🤍🤍🤍

custom 53395416449055787472

Signed 𝐆𝐫𝐚𝐦𝐝𝐢

10 Jul 2026, 11:50 UTC419 views2 reactionsread 3 September 2026

напоминаю всем подписка на инфо кф и акк кф в тт обязательна !!!

custom 52606231283750957132

Signed 𝐆𝐫𝐚𝐦𝐝𝐢

8 Jul 2026, 22:42 UTC528 views0 reactions3 Starsread 3 September 2026
Photo

⭐️⭐️ 🤩🤩🤩🤩 🤍🤍🤍🤍🤍🤍 🔤егодня у нашего администратора фокры день рождения 🤩 давайте поздравим её и пожелаем ей всего самого наилучшего в комментариях. 🔤 днем рождения фокра 🤍 🤍🤍🤍🤍🤍🤍 🤍🤍

Signed 𝐃𝐢𝐚𝐦

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Mentions

Named by 5 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“𝐃𝐚𝐫𝐤 𝐒𝐩𝐚𝐫𝐤 𝐈𝐧𝐟𝐨” (@dark_spark_kf), 408 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/dark_spark_kf.

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.