Telegram RegisterThe public register of Telegram

Channel

Spill Hit n Run Fonneth.

@HitnRun

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

50subscribers

+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-1002506364348
TypeChannel
Username@HitnRun
DescriptionHandled by @Fonneth.
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/HitnRun

Growth

507 August 2026 — 50 subscribers10 August 2026 — 50 subscribers7 August 202610 August 2026
2 measurements spanning 3 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 49–51 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 11:3150no change
7 Aug 2026, 07:0150first reading

Engagement

15 posts held, back to 14 March 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 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 15 posts for this entry, the most recent from 22 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
171
Videos
1
Links
102

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

Recent posts

22 May 2026, 06:22 UTC233 viewsread 10 August 2026
Photo

Contact person korban: @ujellyous Username & ID pelaku: @pleadser 7661474783 Link proof bid pelaku:https://t.me/Fonneth/60488?comment=252566 Kronologi kejadian: gaada balesan samsek buat pay nya:)

21 May 2026, 06:03 UTC235 viewsread 10 August 2026
Photo

LIST BLACKLIST (OWNER GIFT). Username & ID pelaku: @Enginesse & 8392504116 Link Gift: https://t.me/nft/FreshSocks-55663 Channel Terhubung: @InRedness Kronologi kejadian: Gift yang di offer belum bisa di tfo hingga 6 hari kedepan, bidder sudah bersedia untuk menunggu dengan cara menginap di rekber tetapi owner gift tidak bersedia untuk membayar fee menginap dan malah cancel secara sepihak. Kalimat yang diujarkan oleh

13 May 2026, 14:20 UTC216 viewsread 10 August 2026
Photo

Contact person korban: @taylorsawift Username & ID pelaku: @haIamaaadrid Link proof bid pelaku: https://t.me/Fonneth/59261 Kronologi kejadian: Tidak memberikan respon apapun kepada owner gift ketika akan melakukan transaksi setelah offer berakhir.

3 May 2026, 14:50 UTC246 viewsread 10 August 2026
Photo

LIST BLACKLIST (OWNER GIFT). Username & ID pelaku: @kiiicau & 7835197468 Link Gift: https://t.me/nft/WinterWreath-72626 Channel Terhubung: @terperkosa Kronologi kejadian: Owner gift mengaku tidak ingat bahwa ia sedang meng-offer gift nya di sesi no cancel dan malah melakukan trade gift nya dengan pihak lain sehingga kepemilikan gift nya sudah berubah menjadi milik orang lain sebelum transaksi dengan pemenang bid nya

27 Apr 2026, 03:06 UTC233 viewsread 10 August 2026
Photo

Contact person korban: @dollitdoe Username & ID pelaku: @hirononyull & 1220513990 Link proof bid pelaku: https://t.me/Fonneth/57821?comment=242295 Kronologi kejadian: pelaku tidak memberikan kabar, hanya membaca saja tak lama setelah itu pelaku memblokir korban.

20 Apr 2026, 06:24 UTC251 viewsread 10 August 2026
Photo

Contact person korban: @ferraricharless Username & ID pelaku: @slockeet & 8678721037 Link proof bid pelaku: https://t.me/Fonneth/56869?comment=237287 Kronologi kejadian: Tidak ada kabar lagi setelah bidder/pelaku berkata hendak mengirimkan format ke pihak rekber untuk melakukan transaksi. Sudah coba di rechat beberapa kali juga masih tidak memberikan respon.

20 Apr 2026, 06:20 UTC193 viewsread 10 August 2026
Photo

Contact person korban: @idreammie Username & ID pelaku: @penjuditelekram & 7614219597 Link proof bid pelaku: https://t.me/Fonneth/56883?comment=236755 Kronologi kejadian: Tidak memberikan respon lebih lanjut untuk melakukan transaksi dan malah mempromosikan gift tersebut ke channel pribadinya (wts) padahal belum membayar kepada owner gift tersebut.

2 Apr 2026, 04:06 UTC324 viewsread 10 August 2026
Photo

Contact person korban: @sapphwic Username & ID pelaku: 7885813838 Link proof bid pelaku: https://t.me/giftshunting/221491 Kronologi kejadian: Tidak memberikan respon apapun kepada owner gift ketika akan melakukan transaksi setelah offer berakhir padahal sebelumnya sudah membaca pesan owner gift terkait.

31 Mar 2026, 13:41 UTC304 viewsread 10 August 2026
Photo

Contact person korban: @giemar Username & ID pelaku: @manerm & 7787633718 Link proof bid pelaku: https://t.me/Fonneth/54033?comment=218642 Kronologi kejadian: Pelaku memblokir owner gift ketika owner gift menghubungi pelaku untuk melakukan transaksi lebih lanjut. Pelaku berkata bahwa dia tidak jadi untuk take gift tersebut tanpa alasan apapun.

31 Mar 2026, 13:38 UTC342 viewsread 10 August 2026
Photo

Contact person korban: @Leeadonghyuk Username & ID pelaku: @cherryste & 8056926522 Link proof bid pelaku: https://t.me/Fonneth/54028?comment=218687 Kronologi kejadian: Bidder terus memberikan alasan untuk menghindari owner gift sehingga transaksi tidak dapat dilanjutkan dengan alasan saldo kurang dan tidak bisa melakukan top up karena hujan.

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

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.

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

“Spill Hit n Run Fonneth.” (@HitnRun), 50 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/HitnRun.

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.