Hi sorry bot kita hilang dan grup kita juga hilang huhu

Channel
ABAHMART
@ANGKURINGAN
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
34subscribers
-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 | -1001482193184 |
|---|---|
| Type | Channel |
| Username | @ANGKURINGAN |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/ANGKURINGAN |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 17:20 | 34 | -1 |
| 10 Aug 2026, 23:31 | 35 | no change |
| 7 Aug 2026, 04:07 | 35 | first reading |
Engagement
20 posts held, back to 1 March 2022 — 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 20 posts for this entry, the most recent from 11 July 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
@kanaade @tsukia @sangoonomiya ufs yah ask @abahrobot buat price nya
@junrkyu @juenkyu @jeunkyu ufs yh
hy
.
ufs with fp contact @abahrobot
[HELP FW] WANT TO SELL USERNAME FIXED PRICE @Chaueyoung 105k @gnuren 25k nett @chosno 10k nett @eunbhin 50 netip @woonng 50 netip @yunkyouung 100 netip @ksihyeon 65 nego @pwooyeon 65 nego @JinsouulJung 50 nego tebel @csaibing ask @lohaa @yejinkang 50 nett free @natureloha @xiaotinsg ask @dayueon ask @goejo ask @sasngah 85k netip @hyerjoo 30k nett @hynunjae up 100 @xiioting up 80 Paketan https://t.me/doteproperty/14…
WANT TO SELL USERNAME, BANTING HARGA KARENA MAU LBA. 𑁍 BOY/GIRL GROUP. @Keehjo bo Keeho 15K. 𑁍 ANIME CHARACTER. @Asahinas bo Asahina 20K. @Oikcawa bo Oikawa 15K. @Eitoa bo Eita 12K. 𑁍 MULCHAR. @Tekuun bo Tekun 5K. @Harepin bo Harepin 5K. @Menempuh bo Menempuh 3K. @Smooched bo Smooched 3K. @Prajuurit bo Prajurit 3K. ☎️ : @Goroou, @BisaTajirBot. 💸 : DANA, OVO, GO-PAY, Shopee-Pay, QRIS +1K.
guys yuk beli @voxakuma bantu temenku beli photocard txt
@kimgaaeul juga ufs with fp contact aja bot nya hehehe
@beoomgyuchoi ufs with fp hehehehe contact bot ya kalo penasaran harga nya
want to sell fan book tokyo revengers and komik tokyo revengers vol 19. masih mulus banget, baru dibuka gapernah diapa-apain lagi, kalo tertarik chat @kanaade / @abahrobot btw ini bahasa jepang ya 😬
Showing the 12 most recent of 20 posts we hold for @ANGKURINGAN. 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
Named by 7 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
@saerom · 173 postsBami.
@BeoomgyuChOi · 21 postDAGANG FESS, OPEN PP.
@dagangfess · 62,3571 postday(+)eon
@dayueon · 11 postDOTE n. CO
@doteproperty · 391 postGuren
@gnuren · 11 post@ goejo
@Goejo · 21 posthyejoo
@Hyerjoo · 11 postHyunjae
@hynunjae · 31 post@juenkyu
@juenkyu · 21 postNothing
@junrkyu · 31 postbuy @us8888 - @r_y_n
@menempuh · 11 postoikcawa ^___^
@oikcawa · 11 postmarshallue
@sasngah · 21 postMooi.
@tsukia · 11 post
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.
Handles this channel named that no longer answer
- Dead references
- 22
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 21
- vacant every time we have ever looked
@ANGKURINGAN named 22 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 11 August 2026 – 11 August 2026 · confirmed gone 11 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“ABAHMART” (@ANGKURINGAN), 34 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/ANGKURINGAN.
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.