Telegram RegisterThe public register of Telegram

Channel

a Turkish Boy

@aTurkishBoy

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

12subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002175088964
TypeChannel
Username@aTurkishBoy
Descriptionhttps://t.me/aTurkishBoy/44
CreatedBetween 1 June 2024 and 1 July 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/aTurkishBoy

Growth

127 August 2026 — 12 subscribers12 August 2026 — 12 subscribers7 August 202612 August 2026
2 measurements spanning 5 days. 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 11–13 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 05:4512no change
7 Aug 2026, 13:0312first reading

Engagement

20 posts held, back to 1 July 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 20 posts for this entry, the most recent from 26 December 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
4

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

19 reactions across 3 posts, in 5 distinct kinds. The most used accounts for 42.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5363943823720333444842.1%
custom 6273918755177238612421.1%
custom 6275986013131116069421.1%
👍210.5%
custom 606193864282839873215.26%

Custom emoji. 4 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 areTelegram’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 3 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 19reactions 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 1 July 2024 to 26 December 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

21 Oct 2024, 19:15 UTC182 viewsread 12 August 2026

/summon vindicator ~ ~ ~ {CustomNameVisible:1b,Johnny:1b,CustomName:'{"text":"Johnny"}'}

20 Oct 2024, 19:49 UTC221 viewsread 12 August 2026

▫️ /give @p[name="Mani16799"] oak_planks 3 ▫️ Give item(s) to a player. ▫️▫️▫️▫️▫️▫️ @Mani16799

19 Oct 2024, 11:18 UTC183 viewsread 12 August 2026

▫️ /summon minecraft:wolf ~ ~ ~ {Tags:["new"]} ▫️ /data modify entity @e[tag=new,limit=1] AngryAt set from entity @e[type=iron_golem,sort=nearest,limit=1] UUID ▫️ /tag @e[tag=new] remove new ▫️ Summon a new Wolf to fight with the Iron Golem. ▫️▫️▫️▫️▫️▫️ @Mani16799

19 Oct 2024, 11:18 UTC145 viewsread 12 August 2026

▫️ /summon minecraft:evoker_fangs ~ ~ ~ ▫️ Summon Evoker Fangs. ▫️▫️▫️▫️▫️▫️ @Mani16799

19 Oct 2024, 11:18 UTC147 viewsread 12 August 2026

▫️ /summon minecraft:rabbit ~ ~ ~ {RabbitType:99} ▫️ Summon a Killer Bunny. ▫️▫️▫️▫️▫️▫️ @Mani16799

19 Oct 2024, 11:17 UTC129 viewsread 12 August 2026

/attribute Mani16799 minecraft:generic.armor base set 71 @aTurkishBoy - @Mani16799

19 Oct 2024, 11:17 UTC127 viewsread 12 August 2026

/effect give Mani16799 minecraft:speed 100 19 @aTurkishBoy - @Mani16799

19 Oct 2024, 11:17 UTC126 viewsread 12 August 2026

▫️ /item replace entity @p[name="Mani16799"] armor.head with glass 1 ▫️ Putting a Glass On a Player's Head. ▫️▫️▫️▫️▫️▫️ @Mani_16799

19 Oct 2024, 11:17 UTC130 viewsread 12 August 2026

▫️ /summon minecraft:skeleton ~ ~1 ~ {HandItems:[{}]} ▫️ Summon a Skeleton Without Any Item In His Hand. ▫️▫️▫️▫️▫️▫️ @Mani_16799

19 Oct 2024, 11:16 UTC105 viewsread 12 August 2026

▫️ /summon zombie ~ ~1 ~ {HandItems:[{id:"minecraft:golden_axe",count:1},{}]} ▫️ Summon a Zombie Holding a Golden Axe. ▫️▫️▫️▫️▫️▫️ @Mani_16799

19 Oct 2024, 11:16 UTC109 viewsread 12 August 2026

▫️ /attribute @p[name="Mani16799"] minecraft:generic.max_health 100 ▫️ /effect give @p[name="Mani16799"] regeneration 150 1 ▫️ Set a Player Max Health To 100 And Fill It Up One By One In 150 Second. ▫️▫️▫️▫️▫️▫️ @Mani_16799

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

Mentions

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

“a Turkish Boy” (@aTurkishBoy), 12 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/aTurkishBoy.

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.