Telegram RegisterThe public register of Telegram

Channel

☕️Koingopi

@Koingops

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

81subscribers

+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-1001449505084
TypeChannel
Username@Koingops
DescriptionSharing Chart, Update News, Ngopi. ☕️ Bukan Signal, DYOR. Not Financial Advice. RiskReward berada di jari masing-masing. 🥳
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/Koingops

Growth

817 August 2026 — 81 subscribers9 August 2026 — 81 subscribers7 August 20269 August 2026
2 measurements spanning 2 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 80–82 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 18:3181no change
7 Aug 2026, 06:5681first reading

Engagement

17 posts held, back to 27 February 2022the 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 17 posts for this entry, the most recent from 29 January 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
419
Videos
9
Links
276

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

29 Jan 2024, 16:00 UTC188 viewsread 9 August 2026
Forwarded from @glassnodePhoto

Assessing the severity of Bitcoin Bull Market Corrections by cycles, an increased level of resilience can noted across our current cycle. Currently, the largest drawdown has reached a value of only -20.1%, paling in comparsion to historical precedence. For further information on Bitcoin Price Performance, please visit our Dashboard: https://glassno.de/40Xt7GQ

24 Jan 2024, 07:36 UTC163 viewsread 9 August 2026
Forwarded from @glassnodePhoto

With the Bitcoin ETF becoming a classic sell-the-news event, we explore the market's risk appetite for tokens further out on the risk curve. There are some indicators alluding to Ethereum outperformance, as well as interesting divergences in altcoin price action relative to the majors. Discover more in the latest Week On-Chain👇 https://glassno.de/3Hszc6P

17 Apr 2023, 16:36 UTC434 viewsread 9 August 2026

Is the #Bitcoin bear market over? With a rally 100% off the lows, $BTC is trading above a very large cluster of supply, that formed the 2022 floor. This week, we investigate indicators showing if the market making a robust bear market recovery...or not. Read more in The Week On-chain

17 Mar 2023, 08:12 UTC165 viewsread 9 August 2026
Forwarded from @glassnodePhoto

#Bitcoin has now confidently broken above the Adjusted Realized Price located at $24.6k. This average cost basis variant excludes the tremendous profit held by lost coins. The market also recently found support on the classic Realized Price at $19.8k. 📊Live Chart

25 Jul 2022, 17:57 UTC417 viewsread 9 August 2026

https://t.me/glassnode Pioneering on-chain market analysis. Advanced charts/data/insights for investors in Bitcoin and digital assets. https://studio.glassnode.com/

26 Apr 2022, 20:11 UTC343 viewsread 9 August 2026

https://twitter.com/aurelienohayon/status/1518973291490422785?s=21&t=C0nhNjxOhbrPnaMTgCcR_A

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

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

“☕️Koingopi” (@Koingops), 81 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Koingops.

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.