Telegram RegisterThe public register of Telegram

Channel

DragonFox Development (spes/spen)

@dragonfox_spes

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

62subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002023941604
TypeChannel
Username@dragonfox_spes
DescriptionDragonFox Channel for spes/spesn Development DragonFox, is a duo of developers - @TotallyNotH & @KrutosX Here we support the device Redmi note 11 (spes/spesn)
Created24 February 2024measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/dragonfox_spes

Growth

628 Aug 2026, 22:16 — 62 subscribers10 Aug 2026, 04:01 — 62 subscribers8 Aug 2026, 22:1610 Aug 2026, 04:01
2 measurements spanning 1 day. 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 61–63 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 04:0162no change
8 Aug 2026, 22:1662first reading

Engagement

7 posts held, back to 24 February 2024the 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.

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 19 May 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
4
Links
3

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

Reaction mix

59 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 32.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1932.2%
❤‍🔥1322.0%
👍1322.0%
😢1016.9%
🥰23.39%
👎11.69%
🤩11.69%

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 6 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 59reactions 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 24 February 2024 to 19 May 2024, 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

19 May 2024, 18:09 UTC415 views14 reactionsread 10 August 2026
Forwarded from @Elixir_Updates

Well, important announcement! It's been a good time having you guys in the community for the last two years. And I'm very thankful to all the users who have supported us every time when we needed. We have already apologised, but people doesn't get our point and it's fine. You are free to spread misinformation. Still, I will request users who believe in our project for the last two years, you can do a fact Check by

😢102👍2

28 Apr 2024, 18:22 UTC560 views4 reactionsread 10 August 2026
Forwarded from @Elixir_UpdatesPhoto

Project Elixir OFFICIAL - Android 14.0 Update Device: Redmi Note 11 (spes) Maintainer: dragonfox_spes Rom Version: 4.2 Build Date: 2024-04-25 18:31:00 UTC Source Changelogs: Here Device Changelogs: Here Installation Guide: Here Screenshots: Here MD5: d7662948e4be98b424a3fef3bcfda795 Do consider donating if you want to appreciate our work UPI: dwarmachine24@oksbi PayPal: https://www.paypal.me/uglykid24 Patreon: ht

4

20 Apr 2024, 06:10 UTC640 views20 reactionsread 10 August 2026
Forwarded from @Elixir_UpdatesPhoto

Project Elixir OFFICIAL - Android 14.0 Update Device: Redmi Note 11 (spes) Maintainer: dragonfox_spes Rom Version: 4.2 Build Date: 2024-04-15 15:06:00 UTC Source Changelogs: Here Device Changelogs: Here Installation Guide: Here Screenshots: Here MD5: 04a01e571cabc5ee2e15d807cf4559f1 Do consider donating if you want to appreciate our work UPI: dwarmachine24@oksbi PayPal: https://www.paypal.me/uglykid24 Patreon: ht

❤‍🔥13👍32🤩1🥰1

24 Feb 2024, 14:02 UTC946 views13 reactionsread 10 August 2026
Forwarded from @Elixir_UpdatesPhoto

Project Elixir OFFICIAL - Android 14.0 Update Device: Redmi Note 11 (spes) Maintainer: dragonfox_spes Rom Version: 4.1 Build Date: 2024-02-22 09:46:00 UTC Source Changelogs: Here Device Changelogs: Here Installation Guide: Here Screenshots: Here MD5: c4ef19fcfd2e67c46abb92425b666d2f Do consider donating if you want to appreciate our work UPI: dwarmachine24@oksbi PayPal: https://www.paypal.me/uglykid24 Patreon: ht

11👎1🥰1

24 Feb 2024, 13:15 UTC913 views8 reactionsread 10 August 2026
Photo

# Welcome! We are DragonFox - Team of two developers - @TotallyNotH and @KrutosX, developing stuff for different devices Our other channels: - Exynos 9611 Development: @dragonfoxxo

👍8

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

Citation-graph rank — 761,131 of 1,345,403entries 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 2 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.

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

“DragonFox Development (spes/spen)” (@dragonfox_spes), 62 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/dragonfox_spes.

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.