Telegram RegisterThe public register of Telegram
Telegram profile photo for INFO SCAMMER

Channel

INFO SCAMMER

@Hscmer

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

60subscribers

-1 since we began measuring on 19 August 2026

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

Register entry

Telegram ID-1002162243957
TypeChannel
Username@Hscmer
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live3 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 3 September 2026
On Telegramt.me/Hscmer

Growth

606160.519 August 2026 — 61 subscribers19 August 2026 — 61 subscribers27 August 2026 — 60 subscribers19 August 202627 August 2026
3 measurements spanning 7 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 60–61 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 07:1360-1
19 Aug 2026, 23:0061no change
19 Aug 2026, 22:4561first reading

Engagement

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

Recent posts

5 Aug 2026, 15:36 UTC19 viewsread 19 August 2026
Forwarded from @GHClone4Bot

🆔 ID: 8933583668 #id8933583668 👱 Nama: merelyn. 🌐 Username: @iSoftlyy 👀 Situasi: Tidak bergabung

5 Aug 2026, 15:36 UTC19 viewsread 19 August 2026
Photo

LAPORAN PENIPUAN Nama & Username pelaku :: @iSoftlyy Nama & Username clone pelaku :: gatau Nama & Username korban :: @okokcser Nomor ewallet pelaku :: qris dia Store pelaku :: https://t.me/charmilouw Ditipu apa dan berapa :: robux 13.700k Kronologi ::aku pngn beli viplus, aku tf trus pas aku tf dia ga respon, malah gajelas'in aku This bot was made using @LivegramBot

2 Aug 2026, 14:50 UTC20 viewsread 19 August 2026
Photo

LAPORAN PENIPUAN Nama & Username pelaku ::maichan @maichanstore Nama & Username clone pelaku :: maichan @maichanstore Nama & Username korban ::Diana @dinoosaurss Nomor ewallet pelaku :: store pelaku :: https://t.me/maichanstock Ditipu apa dan berapa :: robux 24rb Kronologi :: mau beli robux kebetulan Nemu store dia di lpm, niatnya mau nyoba 100r dulu tp katanya minimal 200r, yauda lanjut di tf, pas Uda di TF chatnya

23 Jul 2026, 07:58 UTC33 viewsread 19 August 2026
Photo

LAPORAN PENIPUAN Nama & Username pelaku :: @caylacarpenter Nama & Username clone pelaku :: gatau…. t__t Nama & Username korban :: @heevvn Nomor ewallet pelaku :: dia pake qris Store pelaku :: dia make store ini Ditipu apa dan berapa :: 150 robux viplus 21k Kronologi :: aku tuh lagi cari robux agak lewat malem gitu di @basewib terus liaat kakak ini pertama aku sung hit aja soalny temen ku pada nunggu terus itu aku ta

23 Jul 2026, 07:57 UTC33 viewsread 19 August 2026

Update on lunastic (REMINDER PENIPUAN) : Info : jual acc korblox dgn harga 400k keatas Bukti/search : https://t.me/penipu_lunasticq_bau_kanjut https://t.me/blklistpenipu/61?single

9 Jun 2026, 13:24 UTC86 viewsread 19 August 2026

LAPORAN PENIPUAN Nama & Username pelaku :: @rallymons Nama & Username clone pelaku :: @oting1933 Nama & Username korban :: - Nomor ewallet pelaku :: - Store pelaku :: @lunasticq Ditipu apa dan berapa :: - Kronologi :: ituu ada kak korbannya dii roblox guard, ada list kalau storenya itu penipuu, jadi buat mencegah kick saja kakakkk, oiya kak, ituu yang namanya "lunasticq.bot" ada banyak dii gc kaka, ituu akun clone d

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“INFO SCAMMER” (@Hscmer), 60 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/Hscmer.

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.