Telegram RegisterThe public register of Telegram
Telegram profile photo for 🪾🪦 ─── artifaacts.

Channel

🪾🪦 ─── artifaacts.

@artifaacts

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

188subscribers

-11 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003186299904
TypeChannel
Username@artifaacts
CreatedBetween 1 September 2025 and 31 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live8 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/artifaacts

Growth

188199193.513 August 2026 — 199 subscribers13 August 2026 — 199 subscribers22 August 2026 — 194 subscribers29 August 2026 — 190 subscribers8 September 2026 — 188 subscribers13 August 20268 September 2026
5 measurements spanning 26 days, net -11. 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 186–201 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 20:38188-2
29 Aug 2026, 20:08190-4
22 Aug 2026, 18:17194-5
13 Aug 2026, 20:02199no change
13 Aug 2026, 19:49199first reading

Engagement

20 posts held, back to 9 August 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.

ERR · 30 days
8.27%
avg views ÷ 188 subscribers
Avg views / post
15.5
11 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
11
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 August 2026
Posts held20 (9 August 202613 August 2026)
Views total171
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 20:02 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

13 Aug 2026, 08:39 UTC5 viewsread 13 August 2026
Forwarded from @proofgawqon

temen temen boleh tolong bantu subs @gawqon please, buat proof bisa di check di @proofgawqon dan tolong sekalian bantu di hfw in 😞😞😞😞. please siapapun yang keep itu tolong balikin ke aku @bhrent

Signed Kei. @fushigurov

13 Aug 2026, 08:39 UTC7 viewsread 13 August 2026

Morning Sketchedd. Baru denger salah satu username kami, @rraden dipakai di bio scammer, and for scamming purposed too. Dia nipu nokos verif & prem app, dan korbannya apparently nggak sedikit. Yang ngelaporin ke bot kami juga habis ditipu dia. Be cautious always and be careful with @mascuIinle PENIPU & NGAKU-NGAKU USERNAME ORANG. Testinya baik-baik but still doesn't prove he is innocent. Be a smart buyer, do cross ch

Signed Kei. @fushigurov

13 Aug 2026, 08:38 UTC13 viewsread 13 August 2026
Forwarded from @darIling

HFW ‼‼ haloo aku baru aja kecolongan usn @iring, boleh minta tolong untuk subs ch nya dan pasang dn 'return @iring to @strawberryy' gak yaa? terimakasih banyak sebelumnya, untuk proof nya ada disini yaa @proofiring. mohon bantuannya temen-temen 😔😔🙏🏻

Signed Kei. @fushigurov

12 Aug 2026, 11:49 UTC23 viewsread 13 August 2026

#Sibu Hi Bu, USN gua baru aja ke keep pas gua mau pindahin ke account sebelah.. karna belum bisa tfo, boleh bantu join @.akyah dn return @ to own ga Bu? Bantu hfw jugaa.. proof disini @.returnAkyah, thank you ya Bu ;)

Signed Kei. @fushigurov

12 Aug 2026, 11:49 UTC22 viewsread 13 August 2026

#sibu Hi, bufiess! Tolong bantu aku forward dan join @.kebnho dengan displayname berupa “return to owner” karena buyer aku baru aja kecolongan username tersebut. untuk proof nya ada di @.proofkebnho yaa. Terimakasih banyak bufiess 🤞🏻

Signed Kei. @fushigurov

12 Aug 2026, 11:15 UTC26 viewsread 13 August 2026

#bambu boleh tolong bantu subs @.keonhoahnu ga bu? Usn gua di keep orang. proof nya di @.proofkeonhoahnu thanks beforee

Signed Kei. @fushigurov

12 Aug 2026, 11:15 UTC24 viewsread 13 August 2026

#sibu bu, mohon bantuannya. temenku kecolongan usn @.seumg, proof nya ada di @.proofseumg, terimakasih banyak bu, aku kasian dia galau bgt 🥹🥹

Signed Kei. @fushigurov

12 Aug 2026, 11:12 UTC6 viewsread 13 August 2026
Forwarded from @proofhatkim

(HFW) hallo, boleh tolong bantu subs @hatkim dan kalau boleh pakai dn return to @Shikikkan. terimakasih banyak yaa

Signed Kei. @fushigurov

12 Aug 2026, 11:12 UTC27 viewsread 13 August 2026

#sibu bu, mohon bantuannya yes. Temen gua kecolongan @.lotuhs, proofnya ada di @.prooflotuhs🙏 kasian bat dia, galau parah. Terimakasihh.

Signed Kei. @fushigurov

12 Aug 2026, 11:12 UTC3 viewsread 13 August 2026

#sibu HFW PLEASE @.efdwardsmartin barusan dibeli sama buyer malay ku tapi kecolongan, proof ada di @.efdwardsmartinproof please subs @.efdwardsmartin and put dn " return @ to @.MartinGark " thankyouu

Signed Kei. @fushigurov

12 Aug 2026, 11:01 UTC15 viewsread 13 August 2026
Forwarded from @Norwaste

HFW ‼‼ haloo aku baru aja kecolongan usn @iring, dan usnnya sekarang dipakai pu sama orang. boleh minta tolong untuk chat-in orangnya dan pasang dn 'return @iring to @strawberryy' gak yaa? terimakasih banyak sebelumnya, untuk proof nya ada disini yaa @proofiring. mohon bantuannya temen-temen 😔😔🙏🏻

Signed Kei. @fushigurov

10 Aug 2026, 23:20 UTC19 viewsread 13 August 2026

#sibu @.spillastonf bu minta tolong hfw, aku abis kena tipu :(

Signed Kei. @fushigurov

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 2 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.

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

“🪾🪦 ─── artifaacts.” (@artifaacts), 188 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/artifaacts.

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.