Photo, posted without a caption
❤12custom 54022602878248846889custom 54024951581114685065🤣3

Channel
@DISTRICTCREW
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
122subscribers
+0 since we began measuring on 4 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002013980868 |
|---|---|
| Type | Channel |
| Username | @DISTRICTCREW |
| Description | STORE — t.me/DISTRICT_1704 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/DISTRICTCREW |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 11:22 | 122 | no change |
| 4 Sept 2026, 10:47 | 122 | first reading |
15 posts held, back to 16 July 2025 — 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 15 posts for this entry, the most recent from 9 September 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 4 September 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.
Measured directly from 3 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.
315 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 34.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 107 | 34.0% | |
| custom 5402495158111468506 | 86 | 27.3% | |
| custom 5402260287824884688 | 69 | 21.9% | |
| 🏆 | 41 | 13.0% | |
| 🤣 | 12 | 3.81% |
Custom emoji. 2 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 13 of the 15 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 315 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 16 July 2025 to 9 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Photo, posted without a caption
❤12custom 54022602878248846889custom 54024951581114685065🤣3
Не спим не спим
❤10custom 540226028782488468810custom 54024951581114685066🤣1
Погода не влияет на тренировочный процесс ⚽️
custom 540249515811146850613❤11custom 540226028782488468811
Всех приветствуем Забыли сказать, что выиграли этот "турнир" второй год подряд 🤫 7:3 сыграли финал Следите за новостями команды тут, на этом мы не собираемся останавливаться. DISTRICT CREW
🏆10❤7custom 54024951581114685067
Играем финал сегодня в 19:00 Репино (60.166306, 29.878085) Приезжайте поддержать
❤7custom 54022602878248846884custom 54024951581114685063
Video message, posted without a caption
custom 540226028782488468810custom 540249515811146850610🏆6🤣3
⬆️⬆️⬆️
https://t.me/boost/DISTRICTCREW
DISTRICT CREW 3:0 [ТП] FC Reverse Позже будет дата финала Играем с HUMSTER
custom 54022602878248846883❤2🏆2custom 54024951581114685062
В среду матч с FC Reverse 18:30 Репино (60.166306, 29.878085)
custom 54024951581114685065❤3🏆3custom 54022602878248846883
Ничего говорить не будем, счет все говорит) 14:0 Играем дальше
❤12custom 54024951581114685067🏆5🤣1
Завтра состоится переигровка матча с BEERPONGERS 20:30 Репино. Всех ждем! (60.166306, 29.878085)
custom 54022602878248846884❤3custom 54024951581114685063🏆2
Showing the 12 most recent of 15 posts we hold for @DISTRICTCREW. 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.
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“DISTRICT CREW” (@DISTRICTCREW), 122 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/DISTRICTCREW.
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.