Telegram RegisterThe public register of Telegram
Telegram profile photo for 2Eyes !

Channel

2Eyes !

@eyes2_2eyes1

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

723subscribers

+295 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-1002361422890
TypeChannel
Username@eyes2_2eyes1
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/eyes2_2eyes1

Topic

Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.

Growth

428723575.57 August 2026 — 428 subscribers8 August 2026 — 428 subscribers8 August 2026 — 434 subscribers16 August 2026 — 467 subscribers23 August 2026 — 517 subscribers30 August 2026 — 568 subscribers9 September 2026 — 618 subscribers18 September 2026 — 723 subscribers7 August 202618 September 2026
8 measurements spanning 42 days, net +295. 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 384–767 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 11:38723+105
9 Sept 2026, 12:38618+50
30 Aug 2026, 18:35568+51
23 Aug 2026, 08:38517+50
16 Aug 2026, 18:36467+33
8 Aug 2026, 14:23434+6
8 Aug 2026, 05:19428no change
7 Aug 2026, 18:22428first reading

Engagement

19 posts held, back to 6 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

59 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 86.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5186.4%
🎉711.9%
🐳11.69%

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 14 of the 19 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 59 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 6 August 2026 to 7 August 2026, 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

7 Aug 2026, 13:12 UTC137 views9 reactionsread 8 August 2026

채팅방에 차트 분석 해줬음 하는 종목(티커) 남겨주시면, 제가 쓰레드에 적을 내용이 생깁니다. 한번 채팅방에 궁금하셨던 종목 적어주시면 감사하겠습니다.

9

7 Aug 2026, 12:46 UTC130 views5 reactionsread 8 August 2026

NFP(비농업고용지수) -23K,,, 비농업고용지수가 이렇게 급격하게 감소할 경우에는.... 달러가 약세를 띈다. 미 국채 금리는 내려가고 , 국채 가격은 올라가고 금은 실질금리와 달러가 떨어졌으므로, 금의 상대 매력이 상승하여 강세. 마이크로소프트, 구글, 아마존같은 라지캡들은 미래 이익의 현재가치가 금리 하락에 민감해서 단기 강세를 보일 가능성이 있다. 뭐 유틸쪽도 투자해도 사실 좋다. XLU,NEE,SO,DUK 같은 종목들은 금리 하락 시 배당주의 할인율 부담이 줄어서,, 상대적으로 매력도가 있다. 당신들이 바라는 강세장을 만들려면, 고용이 줄어도 실업률이 안정되었다는 토픽이 필요하고, 임금이 둔화되어야 하고, 미 채권 2년물 금리가 하락해야만 한다. 사실 최근에 금이 상승했던 여력을 보면, 충분히 가능성이 있는 시나리

5

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

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

“2Eyes !” (@eyes2_2eyes1), 723 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/eyes2_2eyes1.

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.