Channel
@cainegroup
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
454subscribers
-6 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001335881052 |
|---|---|
| Type | Channel |
| Username | @cainegroup |
| Created | Between 1 March 2018 and 11 January 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/cainegroup |
Real estate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 70% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 11:02 | 454 | -1 |
| 11 Sept 2026, 02:55 | 455 | -1 |
| 2 Sept 2026, 10:34 | 456 | -2 |
| 19 Aug 2026, 23:54 | 458 | -2 |
| 13 Aug 2026, 11:15 | 460 | no change |
| 13 Aug 2026, 03:32 | 460 | first reading |
20 posts held, back to 11 January 2021 — 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 5 May 2023. An engagement rate over an empty window would be a number about nothing.
Investment pool open: Our real estate division is buying a portfolio of residential buildings in Canada, raising $3.5m by May 15. Minimum per non-accredited investor is $10K and maximum $25K. Capped at $200K for accredited investors. Payment must be made by wire transfer to our Canadian corporate bank account. The portfolio will be sold within 2 years with an estimated yearly return of 13-18%. The buildings all cas…
China-brokered Saudi-Iran deal and SVB collapse were the events; although no direct involvement from China, it is the main bank for US investment in Chinese co’s. FED responded 4 hrs ago enabling loans of up to 1 year to banks, i.e. unofficial QE: https://www.federalreserve.gov/newsevents/pressreleases/monetary20230312a.htm Mechanisms employed by the Fed are bullish for the crypto narrative as we get closer to the U…
A big geopolitical event will most likely happen between Feb 27 and March 10, involving either China or the Middle East. Starting off Q2 negatively with attempted recovery into April and potentially a first successful reversal going into May/June. Possible a second more positive event around end of April. This is based on drier volume across the board contrasting with past failed reversals, astro and geopolitical adv…
Happy new year. Last year was silent on our part, with main message sent in Dec 2021 highlighting negative sentiment towards the market and VCs leading the frothy metaverse craze. We saw three failed reversals in 2022. Q2 of this year will likely bring a successful reversal fuelled by rate change/added liquidity. Whether this reversal sticks into Q3 will depend on macro & politics but most importantly market tractio…
Here is the Alameda and FTX balance sheet: https://docs.google.com/spreadsheets/d/1dSG6ER9N_YABnmUKzKaeUikZ2-isBQpL/ Time and time again every “cycle” we see shameless greed and over-leveraging by the top funds and projects. Luna, Harmony, and now Alameda. Message sent in December turned out to be true. Most projects were doomed by uncontrolled egos both on sell and buy side. As crypto matures we will see less frothy…
Exiting here at $195 for 30% gain on 3x lev. This was just for fun and closing simply because not wanting to keep position open more than 3 hrs. FINRA margin debt almost at one trillion, interest rate fear, 10yr treasury yield fall, VCs throwing money at anything that moves, thinking crypto is a “hedge” to inflation and that web3 is their gateway to riches, are signs that there will be another multi-week pull back af…
Buying $SOL here at $175
Look into Polkadot and Kusama parachain auctions. Teams are held accountable and do not receive any funds for the duration of their parachain lease time (1yr for KSM and 2yrs for DOT). Kusama is a Polkadot parachain hosting its own parachains. Top current crowdloans on auction are Bit.country, Zeitgeist on KSM and Acala, Moonbeam, Astar on DOT. Main layer 1 & 2 challenges can be solved with layer 0 scalability and i…
Longing BTC here at $40,700 40% position size other longs at 38,200 and 39,400
Foreseeing more downside but wanted to close the position within 24 hrs so closing here at $3,800 for 40% profit on 6x
Shorting $ETH here at $4,050
Closing other half of $HBAR here at a little over breakeven, not liking the price action
Showing the 12 most recent of 20 posts we hold for @cainegroup. 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.
Named by 1 registered channel — 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.
@cainegroup named 2 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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“Caine Group” (@cainegroup), 454 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/cainegroup.
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.