Telegram RegisterThe public register of Telegram
Telegram profile photo for Hanyar samun kuɗi a online 🎊

Channel

Hanyar samun kuɗi a online 🎊

@ameenuking

On this record: Topic · Growth · Engagement · Posts · Cite this entry

5subscribers

+1 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-1003604516128
TypeChannel
Username@ameenuking
Created18 January 2026 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live15 November 2026
Measurements held3
Confirmed unchanged3 times, most recently 15 November 2026
On Telegramt.me/ameenuking

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 29 October 2026 and assigned it the closest of 31 fixed categories, at 59% 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 the other topics.

Growth

454.57 August 2026 — 4 subscribers13 August 2026 — 4 subscribers29 October 2026 — 5 subscribers7 August 202629 October 2026
3 measurements spanning 83 days, net +1. 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 4–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Oct 2026, 21:155+1
13 Aug 2026, 07:464no change
7 Aug 2026, 18:184first reading

Engagement

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

Recent posts

18 Jan 2026, 10:36 UTC62 viewsread 13 August 2026

Gargadi 🚫 ‎ ‎Ba kowanna Link akeshiga ba.🔗 ‎ ‎🚫. Kar ka danna link ɗin da ba ka sani ba Duk wanda yaturo maka link a Facebook, kar ka danna shiga wannan account din kaduba MUTUNNE Sananne kokuma aranar kafara saninsa INBAKA bincike kafin kashiga Link account dinka kanagab darasashi hacking ne. 😱 ‎ ‎🚫.Kar ka tura lambar wayarka 📞: Duk wanda yace katuro masa lambar wayarka zai sanyama data ko kati kyauta, kar ka tura…

Signed Ameenuh King

Showing the 6 most recent of 6 posts we hold for @ameenuking. 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.

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

“Hanyar samun kuɗi a online 🎊” (@ameenuking), 5 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/ameenuking.

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.