LFG

Channel
aLpHa ChArTs
@itsalphabro
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
3subscribers
+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 | -1001655375987 |
|---|---|
| Type | Channel |
| Username | @itsalphabro |
| Description | I find alpha charts and post them :) *disclaimer This is just for fun nfa dyor |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/itsalphabro |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 12:18 | 3 | no change |
| 7 Aug 2026, 09:51 | 3 | first reading |
Engagement
20 posts held, back to 2 July 2023 — 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 21 July 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 11
- Videos
- 1
- Links
- 6
Lifetime counters from Telegram’s own channel header, read 13 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.
Reaction mix
3 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 33.3% | |
| 🔥 | 1 | 33.3% | |
| 😁 | 1 | 33.3% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 3 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 2 July 2023 to 21 July 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Or banned me
Hopeium gone they deleted chat
This one came from a based dev that’s had 2 utility projects this week! (I know dev must be full force chad!!) Anyway this one has 4/4 tax plus supply in the contract, not to mention 16 airdropped wallets (dev has charity too it seems) It appears the community let this one die, dev did hard marketing with trending and even updated dextools!! Made a huge dent in the 10 or so eth collected from taxes as well I imagin…
🔥1
New alpha incoming
This was a solid alpha! Community let this die after dev worked extremely hard! Dev BUNRT 8% of the supply and even got a call from kobi. 0/2 tax and lp was locked. @PepeLiteEntry Printability 6/10 if you bought when dev shook the bots you could of done a very easy 10x! If you bought at Kobis call you where exit liq. For early calls follow @cryptoneecalls
Weak alpha play today! One good pump in it was the highlight of this alpha!! I think community where lacking intelligence, they sold hard while the dev did dev stuff. Printability 7/10. Entry was easy and had a 5-6x potential
@pawtwoerc Look at this solid alpha from a safe dev! Jeets rekt this one by letting the dev send supply to himself and sell. Devs just can’t get a break in this space with investors like this. Printability 3/10 could of had a 2x from dump @10k to 20k
😁1
We got an alpha incoming!!!!!!
Dev eating well
Report by @TaxInspector_Bot FOREVER CR7 – $CR7 (ETH) 🔍 Token info (chart): ├─ Started – 2 hours ago ├─ Honeypot.is passed ✓ └─ Taxes are 0% / 0% 👨 Deployer 0x481...ee (0 USD): ├─ Created 2 hours ago └─ Funded from FixedFloat, 1.51 ETH 💬 Socials: ├─ t.me/cr7erc ├─ forevercr7.live └─ twitter.com/cr7oneth 💵 Tax report: ├─ 6.71 ETH or 11,265 USD └─ No buybacks were made 💼 Deployer 0x481...ee (got 100%): ├…
Whenever I see a chart like this with burnt lp and 0/0 tax I just know it’s the dev securing his profit. Devs have to make money guys, burnt lp with 0/0 tax adds risk to the dev. That risk is passed on to you when he keeps 20% supply in the contract! Anyway lp is burnt so this could actually have a community revival Printability 7/10 as it had a really good run up first @cr7erc
Showing the 12 most recent of 20 posts we hold for @itsalphabro. 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.
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.
Handles this channel named that no longer answer
- Dead references
- 3
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 3
- vacant every time we have ever looked
@itsalphabro 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 August 2026
named in 1 post, 14 August 2026 – 14 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“aLpHa ChArTs” (@itsalphabro), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/itsalphabro.
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.