Channel
@footbalkurd
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
220subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001130069583 |
|---|---|
| Type | Channel |
| Username | @footbalkurd |
| Description | که نالی مه یی دیتر فولو بکه ن @TNEBONN |
| Created | Between 1 June 2017 and 31 August 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/footbalkurd |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 03:18 | 220 | no change |
| 6 Aug 2026, 12:21 | 220 | first reading |
20 posts held, back to 1 January 2023 — 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 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 20 posts for this entry, the most recent from 27 July 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
دەم باش هەفالان بو هەمی قوتابیان و وان هەفالێت حەز لسەر فان جورە بابەتان هەبیت کەنالێ ماموستا نیهاد جوین بکەن تایبەت گرێدای بابەتێ بیرکاری بو هەمی قوناغان دێ گەلەک مفای ژئ بینن هەمی بابەت و پسیار یئت ویزاری ٩،١٢ تیدا بینن😍📚📐 https://t.me/nihadkamil
Signed حۣۗـྀہمۣۗـڪٰ✠ٰ๋ۗٛۧۙۙ͜͡ـٍٰۗٛۧۙۙ℘ـٌٍِٰٰٰٰٰٖٖٖٖٖٖٖٖ۪ٖ۫ۗٛۧۙۙوِ
https://t.me/hamsTer_kombat_bot/start?startapp=kentId668127710 Play with me, become cryptoexchange CEO and get a token airdrop! 💸 +2k Coins as a first-time gift 🔥 +25k Coins if you have Telegram Premium
Signed RHB
Posted without readable text
Signed RHB
https://t.me/hamster_kombat_bOt/start?startapp=kentId668127710 Play with me, become cryptoexchange CEO and get a token airdrop! 💸 +2k Coins as a first-time gift 🔥 +25k Coins if you have Telegram Premium
Signed RHB
Bo wan havalet maina dgel me em del vere berdawam bin o kanalake ni https://t.me/+COvziZo57zA0ZjQy
Signed RHB
Posted without readable text
Signed Rashad
Posted without readable text
Signed Rashad
https://t.me/tnebonn
Signed Rashad
Posted without readable text
Signed Rashad
Posted without readable text
Signed Rashad
Posted without readable text
Signed Rashad
Posted without readable text
Signed Rashad
Showing the 12 most recent of 20 posts we hold for @footbalkurd. 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 — 1,091,067 of 1,336,469entries 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.
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.
Named by 8 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Football kurdish” (@footbalkurd), 220 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/footbalkurd.
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.