Telegram RegisterThe public register of Telegram
Telegram profile photo for Kevin De Bruyne

Channel

Kevin De Bruyne

@DeBruyneKev

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

2,557subscribers

-37 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001174478720
TypeChannel
Username@DeBruyneKev
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live8 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/DeBruyneKev

Growth

2,5572,5942,575.56 August 2026 — 2,594 subscribers6 August 2026 — 2,594 subscribers10 August 2026 — 2,591 subscribers14 August 2026 — 2,582 subscribers17 August 2026 — 2,576 subscribers20 August 2026 — 2,567 subscribers24 August 2026 — 2,572 subscribers27 August 2026 — 2,571 subscribers30 August 2026 — 2,568 subscribers3 September 2026 — 2,564 subscribers8 September 2026 — 2,557 subscribers6 August 20268 September 2026
11 measurements spanning 33 days, net -37. 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 2,551–2,600 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 11:422,557-7
3 Sept 2026, 06:462,564-4
30 Aug 2026, 15:342,568-3
27 Aug 2026, 17:322,571-1
24 Aug 2026, 19:232,572+5
20 Aug 2026, 21:462,567-9
17 Aug 2026, 13:472,576-6
14 Aug 2026, 13:332,582-9
10 Aug 2026, 20:512,591-3
6 Aug 2026, 16:342,594no change
6 Aug 2026, 16:272,594first reading

Engagement

17 posts held, back to 10 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 17 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

870 reactions across 17 posts, in 9 distinct kinds. The most used accounts for 54.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
47854.9%
💔21224.4%
🔥697.93%
❤‍🔥667.59%
😭212.41%
🫡101.15%
😢60.69%
👍50.575%
😍30.345%

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

Measured over the 17 most recent posts we hold, published 10 July 2026 to 27 July 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

27 Jul 2026, 20:57 UTC544 views71 reactionsread 7 August 2026
Photo

🇳🇱🇧🇪 | تعطیلات کوین در کنار ویرجیل فن‌دایک. 🇧🇪 @DeBruyneKev

60🔥6❤‍🔥4😍1

Signed S-S

24 Jul 2026, 22:27 UTC897 views90 reactionsread 7 August 2026
Photo

🚨نیکولو شیرا : کار کوین با ناپولی تمومه! 🇧🇪 @DeBruyneKev

67😭16💔6🔥1

Signed S-S

24 Jul 2026, 19:50 UTC840 views39 reactionsread 7 August 2026
Photo

🚨🇧🇪 مانا مدیر ناپولی، در مورد تصمیمات مربوط به آینده کوین : چیزی برای تصمیم‌گیری وجود ندارد. او یک سال دیگر با ما قرارداد دارد به علاوه گزینه‌ای برای ماندن یک فصل دیگر؛ من شخصاً از آنچه کوین در ماه مه گفت خوشم نیامد؛ اما وقتی برگردد، در موردش صحبت خواهیم کرد. 🇧🇪 @DeBruyneKev

34❤‍🔥2💔2🔥1

Signed S-S

22 Jul 2026, 16:56 UTC870 views69 reactionsread 7 August 2026
Photo

🌐استوری اینستاگرام کینگ کوین: 🇧🇪 @DeBruyneKev

🔥4718❤‍🔥3💔1

Signed S-S

19 Jul 2026, 01:28 UTC974 views54 reactionsread 7 August 2026
Photo

🌐استوری اینستاگرام اسطوره کوین در کنار ناتان آکه و فن دایک 🇧🇪 @DeBruyneKev

47❤‍🔥4🔥3

11 Jul 2026, 13:39 UTC≈1,220 views61 reactionsread 7 August 2026
Photo

📲 پست جدید کوین در اینستاگرام: ماجراجویی ما در جام جهانی همین‌جا به پایان رسید. با سربلندی سرمان را بالا نگه می‌داریم. به این تیم و کشورمان بی‌نهایت افتخار می‌کنیم! 🇧🇪❤️ 🆔 @DeBruyneKev

56❤‍🔥5

10 Jul 2026, 21:28 UTC≈1,320 views85 reactionsread 7 August 2026
Photo

اونانا بازی قبلی رباط میده تیلمانس در حال گرم کردن مصدوم میشه کورتوآ مصدوم میشه کوین نتونست ادامه بده واقعا ته بدشانسی بود 🆔 @DeBruyneKev

💔754😢4👍2

10 Jul 2026, 21:10 UTC≈1,030 views73 reactionsread 7 August 2026
Photo

و آخرین بازماندگان نسل طلایی بلژیک هم به پایان رسیدن 💔 🆔 @DeBruyneKev

💔66😭5😢2

10 Jul 2026, 21:04 UTC857 views67 reactionsread 7 August 2026
Photo

متاسفانه بلژیک با اشتباه لامنس از جام جهانی 2026 حذف شد 🆔 @DeBruyneKev

💔624👍1

10 Jul 2026, 19:05 UTC758 views35 reactionsread 7 August 2026
Photo

شروع بازی؛ به امید پیروزی و صعود 🇧🇪❤️ 🆔 @DeBruyneKev

35

10 Jul 2026, 18:38 UTC778 views30 reactionsread 7 August 2026
Photo

در حال گرم کردن 🔥 🆔 @DeBruyneKev

❤‍🔥234🔥3

10 Jul 2026, 18:26 UTC854 views27 reactionsread 7 August 2026
Photo

👑 🆔 @DeBruyneKev

18❤‍🔥7🔥1😍1

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

منچسترسیتی | Mancity منچستر سیتی
@ManchesterCityTM · 44,627
Telegram ranks this channel #46 of 90 here — alongside 89 others — read 28 August 2026
UEFA Champions League
@UEFA_Champions_League_Worldwide · 37,478
Telegram ranks this channel #56 of 73 here — alongside 72 others — read 5 September 2026
Manchester City 🩵
@ManCityFRa · 29,182
Telegram ranks this channel #59 of 73 here — alongside 72 others — read 8 September 2026
MAN CITY XTRA™
@MAN_CITY_XTRA · 118,317
Telegram ranks this channel #70 of 72 here — alongside 71 others — read 14 August 2026
Manchester City
@mancity247 · 45,736
Telegram ranks this channel #85 of 94 here — alongside 93 others — read 27 August 2026
Manchester City FC
@manchester_city · 129,666
Telegram ranks this channel #86 of 93 here — alongside 92 others — read 13 August 2026

This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Kevin De Bruyne” (@DeBruyneKev), 2,557 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/DeBruyneKev.

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.