Telegram RegisterThe public register of Telegram
Telegram profile photo for Kripto Airdrop Turkiye

Channel

Kripto Airdrop Turkiye

@kripto_madencilerii

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

449subscribers

-265 since we began measuring on 17 August 2026

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

Register entry

Telegram ID-1002052006446
TypeChannel
Username@kripto_madencilerii
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live11 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/kripto_madencilerii

Topic

Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 90% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

449714581.517 August 2026 — 714 subscribers18 August 2026 — 714 subscribers26 August 2026 — 458 subscribers2 September 2026 — 452 subscribers11 September 2026 — 449 subscribers17 August 202611 September 2026
5 measurements spanning 25 days, net -265. 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 409–754 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 13:56449-3
2 Sept 2026, 13:07452-6
26 Aug 2026, 01:32458-256
18 Aug 2026, 00:58714no change
17 Aug 2026, 20:15714first reading

Engagement

20 posts held, back to 25 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 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 20 posts for this entry, the most recent from 17 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.0%

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 1 reactions 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 25 July 2026 to 17 August 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

17 Aug 2026, 11:34 UTC11 viewsread 17 August 2026

📢 StarX Network – Bir Sonraki STRX Yarılanması 19 Ağustos’ta Geliyor! ⛏️🚀 StarX Network topluluğuna, bir sonraki STRX madencilik yarılanmasının 19 Ağustos’ta gerçekleşeceğini bildirmek istiyoruz. Bu yarılanma, planlanan STRX emisyon azaltımının bir parçası olarak hem temel madencilik oranını hem de referans teşvik oranını azaltacaktır. ⛏️ Madencilik Oranı Mevcut Madencilik Oranı: 0.1563 STRX/saat Yarılanmadan So

17 Aug 2026, 11:32 UTC10 viewsread 17 August 2026

CPEN Sahipleri Adına @BitMartExchange'e Açık Bir Talep BitMart, 26 Temmuz'da ticaret platformunun kapatılacağını duyurduğundan beri, birçok CPEN sahibini etkileyen bir sorunla ilgili olarak BitMart ile özel olarak iletişime geçtik. Bu kanal üzerinden bir yanıt almadık, bu yüzden şimdi kamuoyu önünde soruyoruz. 16 Ağustos 2026 itibarıyla gerçekler şunlar: 1. CPEN ticareti BitMart'ta pratikte artık mevcut değil. Bit

15 Aug 2026, 17:26 UTC26 viewsread 17 August 2026
Photo

Pi Node sürüm 0.6.2 yayınlandı! Bu sürüm, SoloHost, Node bağlantı özellikleri ve Pi Desktop kullanıcı deneyimine yönelik iyileştirmeler getiriyor. Aynı zamanda, Pi, bir SoloHost uygulaması aracılığıyla dağıtık hesaplama testini başarıyla tamamladı ve Pi Node'ların Pi blok zincirini desteklemenin ötesinde faydasını daha da ilerletti. Bu güncellemeler birlikte, Pi Node'lar ve SoloHost üzerinde uygulamaları çalıştırm

8 Aug 2026, 14:23 UTC63 views0 reactionsread 17 August 2026

📢 StarX Network – Cüzdan Yeniden Gönderim Güncellemesi Artık Canlı! 👛🚀 En son StarX Network güncellemesinin artık canlı olduğunu duyurmaktan memnuniyet duyuyoruz. 👛 Cüzdan Yeniden Gönderim Artık Kullanılabilir Kullanıcılar artık cüzdan adreslerini doğrudan uygulama içinden düzenleyebilir ve yeniden gönderebilir. Daha önce yanlış bir cüzdan adresi gönderdiyseniz veya cüzdanınızı güncellemeniz gerekiyorsa, basitçe:

7 Aug 2026, 14:43 UTC62 viewsread 17 August 2026
Photo

Merhaba #cPenNetwork topluluğu, ⏰ Hatırlatma: INK KYC, Canlılık ve Kilit Son Tarihi INK dağıtımı için KYC ve Canlılık doğrulamasını tamamlamak için son tarih: 📅 13 Ağustos 2026 ⏰ 23:59:59 UTC Lütfen son tarihten önce KYC / Canlılık doğrulamasını tamamladığınızdan emin olun. 🔒 INK Kilit Seçimi INK Kilit seçimi de aynı zamanda sona erecek. Son tarihten önce şunları yapabilirsiniz: • Bir INK Kilit seçeneği seçin

5 Aug 2026, 10:17 UTC61 viewsread 17 August 2026

📢 StarX Network – Yaklaşan Güncelleme Bildirimi 🚀 StarX Network’ün bir sonraki güncellemesinin şu anda geliştirilmekte olduğunu paylaşmaktan heyecan duyuyoruz! 👛 Cüzdan Adresi Düzenleme Seçeneği Gönderilen cüzdan adreslerini güncelleme yeteneği isteyen kullanıcılardan geri bildirim aldık. Cüzdan Adresi Düzenleme seçeneğinin bir sonraki güncellemede yer alacağını duyurmaktan mutluluk duyuyoruz; bu sayede kullanıcı

5 Aug 2026, 08:29 UTC46 viewsread 17 August 2026
Photo

📢 Topluluk Güncellemesi Bir dizi istişare, beyin fırtınası ve kapsamlı teknik değerlendirmenin ardından, yeni SpurProtocol uygulaması güncellemesinin yayında olduğunu duyurmaktan heyecan duyuyoruz! 🚀 Borsa ortaklarımızla fırsatları keşfetmeye devam ederken, mevcut görevleri tamamlayarak aktif olarak katılabilir, ardından desteklenen zincirler genelinde desteklenen merkeziyetsiz cüzdanları kullanarak stake edebilir

5 Aug 2026, 08:27 UTC45 viewsread 17 August 2026
Photo

Bee Coin Eko Sistemine Bağlı Bee Xp Minining için 👇 -Bee com sitesinde Chek in ile giriş yapın -Bee Network uygulamanızla bee com sitesini Authorize edin. -Login - Start - Claim ve görevleri yapın. - Xp gelecekte Bee Coinleri cüzdandan çekim için veya ayrı token olarak kullanılabilir. günlük Bee Xp ödüllerini ücretsiz toplayabilirsiniz. Günlük girişlerde Bee Network uygulamanızın sol üst köşesinden bee com'a ba

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

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.

Cüzdan Haberleri 🇹🇷
@cuzdan_haberleri · 26,751
Telegram ranks this channel #8 of 72 here — alongside 71 others — read 11 September 2026
Baby Doge Duyurular
@BabyDogeAnnTR · 83,961
Telegram ranks this channel #37 of 80 here — alongside 79 others — read 17 August 2026
Pump Arena Channel
@pumparenachannel · 30,103
Telegram ranks this channel #75 of 81 here — alongside 80 others — read 7 September 2026

This channel appears in 3 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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“Kripto Airdrop Turkiye” (@kripto_madencilerii), 449 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/kripto_madencilerii.

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.