Channel
@rikkabscproject
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
86subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001236195381 |
|---|---|
| Type | Channel |
| Username | @rikkabscproject |
| Description | ENTRY BARENG TP BARENG, BANTU SHILL PROJECT YANG DI SHARE DISINI DO WITH YOUR OWN RISK. |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/rikkabscproject |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 16:16 | 86 | no change |
| 6 Aug 2026, 23:44 | 86 | first reading |
20 posts held, back to 23 January 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 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 20 posts for this entry, the most recent from 8 September 2022. An engagement rate over an empty window would be a number about nothing.
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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
HAMTAROBOY Buy! 🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹 💸 1.53 BNB ($426.60) 🪙 5,735,880 HAMB 👤 Buyer 0x2d06…666c | Txn ⏫ Position +45.37% 💰 Market Cap $72,825
WKOWKOWKOWKO
HAMTAROBOY Buy! 🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹🐹 💸 5.916 BNB ($1581.77) 🪙 9,418,320 HAMB 👤 Buyer 0x0000…c760 | Txn ⏫ Position +1000% 💰 Market Cap $231,
I will ape here big soon. Reason: dev is my old old friend and he has bullish project which reach 552M mcap. Also the marketer is bullish who always send project to 2M+ minimun. Let's see about this one now it's sitting on 15k none marketing kicked in but no dip lol. I might ape after the first dip but not sure I am thinking about ape half now as fomo and rest half in first dip from now https://t.me/hamtaroboy
Frog Inu Buy! 🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸 Spent: $15,551.71 (48.5 BNB) Got: 2,521,796,462,346 FGI Buyer Position: New! Price: 0.000000006167 (0.00000000001923 BNB) MCap: $6,166,915 TX | Chart | Buyer | Pancakeswap
OpenNFT Buy! 💚 Spent: $16.03 (0.05 BNB) Got: 3,911 ONFT Buyer Position: ⬆️10.49%! Price: 0.004099 (0.00001278 BNB) MCap: $409,866 TX | Chart | Buyer | Pancakeswap
LZ Buy! 🟢 Spent: $17.32 (0.05 BNB) Got: 27,471,379,800 LZ Buyer Position: ⬆️4.99%! Price: 0.0000000006303 (0.000000000001966 BNB) MCap: $63,030 TX | Chart | Buyer | Pancakeswap
Rohan Doge Buy! 🟢🟢 Spent: $137.63 (0.43 BNB) Got: 8,854,609,332 Rohan Doge Buyer Position: ⬆️110.11%! Price: 0.00000001554 (0.00000000004856 BNB) MCap: $101,030 TX | Chart | Buyer | Pancakeswap
Forget all the program listings to watch RohanDoge solo Tonight's only program list on the whole network RohanDoge Hundreds of communities unite more than 1,000 retail investors with a new Meme The battle of honor for all colleagues in the primary market Launch time: UTC+8:20:00 UTC: 12:00 Contract: 0x1124F849FdcA2dBA8c10eAa41278d4204196b52A Ultra-low slippage: 3 Chinese TG: https://t.me/RohanDogeChinese Ov…
https://t.me/+9MhDVKj_UTk1MjY9
🐩Project name: White Doge Coin (WhiteDoge) 🐶The fouth dog of Putin,Putin loves dogs!He named his newest doge called White！ Born in Russia, White Doge (WDoge) is the newest member of the Doge family and Putin's favorite dog. Born for the good of the metasomes, he is synonymous with love and peace The goal of Dorge is to rebuild the security and trust of the market, treat cryptocurrency investors with heart, come with…
k0king (K0 King) kill zero game One coin with the most 0s in history, 49 0s, kill zero game, go to zero experiment Our slogan is only kill 0, kill 0, kill 0, kill all the 0 we want. So we fired a massive 100,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,00 tokens Create a generation of god coins, go to 0 and start... 10U dream, [10u becomes 10000u] 10,000 times set sail! The permissions have been lost, …
Showing the 12 most recent of 20 posts we hold for @rikkabscproject. 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.
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.
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.
@rikkabscproject named 3 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.
References a handle that is not a live channel — we have no record it ever was one.
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.
“RIKKA PROJECT CHANNEL” (@rikkabscproject), 86 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/rikkabscproject.
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.