이런 구조인데 한순간에 베네수엘라에서 폭발적으로 늘어날거라고 하는건 머리가 나쁜것
🐳5

Channel
@Trillion_labs
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
9,443subscribers
+211 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003402415038 |
|---|---|
| Type | Channel |
| Username | @Trillion_labs |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/Trillion_labs |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 16 Sept 2026, 00:57 | 9,443 | +48 |
| 12 Sept 2026, 18:16 | 9,395 | +44 |
| 9 Sept 2026, 00:00 | 9,351 | +36 |
| 3 Sept 2026, 13:57 | 9,315 | -7 |
| 31 Aug 2026, 06:44 | 9,322 | -1 |
| 28 Aug 2026, 10:36 | 9,323 | +31 |
| 25 Aug 2026, 12:59 | 9,292 | +6 |
| 22 Aug 2026, 13:35 | 9,286 | +31 |
| 19 Aug 2026, 12:12 | 9,255 | +1 |
| 16 Aug 2026, 21:12 | 9,254 | +34 |
| 13 Aug 2026, 05:36 | 9,220 | -8 |
| 9 Aug 2026, 19:41 | 9,228 | -7 |
| 6 Aug 2026, 09:41 | 9,235 | +3 |
| 6 Aug 2026, 03:07 | 9,232 | first reading |
398 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 32 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 114 of 159 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 August 2026 |
|---|---|
| Posts held | 398 (5 August 2026 – 29 August 2026) |
| Views total | 200,662 |
| Reactions total | 606 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 07:15 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 16 videos 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.
1,599 reactions across 246 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🐳 | 1,599 | 100.0% |
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 256 of the 398 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 1,641 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 398 most recent posts we hold, published 5 August 2026 to 29 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.
이런 구조인데 한순간에 베네수엘라에서 폭발적으로 늘어날거라고 하는건 머리가 나쁜것
🐳5
ㄴㄴㄴㄴ 베네수엘라는 굉장히 무겁기 때문에 희석제가 다량 필요함. 희석제 자체조달 능력 부족 미국산 나프타 공급에 의존하는 구조 그럼 베네수엘라 생산량이 늘수록 비톨애들이 희석제 다량으로 보내줘야 하는 구조임.
🐳5
자 그럼 이게 끝?
그야 인프라가 쓰레기이기 때문
왜 베네수엘라가 현재 125만 배럴이 한계에 도달했는가? 고객이 인프라에 접근하는 것이 점점 더 복잡해지고 있습니다. 무역 회사들은 1월 이후 1억 4천만 배럴 이상을 수출했습니다. 최근 몇 달 동안 수출량은 하루 125만 배럴을 넘는 데 어려움을 겪었다는 자료가 있습니다. 마리안나 파라가 지음 베네수엘라의 노후화된 석유 항만 터미널은 최근 회복세를 보이고 있는 이 나라의 원유 생산량에 사실상 수출 상한선을 설정하고 있습니다. 해운 관련 자료와 소식통, 문서에 따르면, 노후화된 기반 시설, 잦은 정전, 그리고 원유 품질 문제로 인해 유조선들은 선적에 최대 30일까지 기다려야 하는 상황입니다. 이러한 지연은 국제 무역 회사들과의 획기적인 합의 이후 베네수엘라 석유 수출을 신속하게 재개하려는 미국의 계획을 방해하고 있습니다. PDVSA…
🐳4
잠이나 자십셔 크랙이 이런다고 떨어진다고 생각하는거면 능지의 문제
CVX > HAL > 유전서비스 업종 이유 시추·보수·펌프·인공양수·전력·희석제·파이프라인 수리가 현재 먼저 단행되어야됨. 따라서 OCTG나 라인파이프 발주는 훨씬 뒤늦게 나올것
🐳6
한미디로 이야기하면 MAGA 지지층 결집을 위한 선전 포스터 매장량=설비량을 동일시 여기는 바보집단만이 휘발유 가격이 떨어질거라고 생각할 수 있다. 미국은 베네수엘라와 세계 역사상 최대 규모의 석유 거래에 관한 합의에 막 들어섰습니다! 내 지시에 따라 마코 루비오 국무장관과 피트 헤그세스 전쟁장관은, 존경받는 베네수엘라 임시 대통령 델시 로드리게스와 긴밀히 협력하고 민간기업과의 파트너십을 통해, 미국 납세자에게 아무 비용도 들이지 않고 베네수엘라에 있는 650억 배럴이 넘는 확인 석유 매장량에 대한 미국의 과반 통제권을 확보했습니다. 이 역사적 거래는 미국의 석유 매장량을 두 배 이상 늘리고 석유 공급을 크게 확대하며, 앞으로 오랫동안 모든 미국인의 휘발유 가격을 상당히 낮출 것입니다. 동시에 베네수엘라가 엄청난 성공과 위대한 번영을 향해 …
🐳6
https://www.youtube.com/watch?v=3HcILu2Nkd8 ai의 발전으로 이제 판타지 드라마를 일반인들이 몇명 모여서 뚝딱할수있게 되어버림. 개인적으로 재밌게봤습니다. 473시간의 작품
🐳3
“이 분야에서 미국의 우위는 선택 사항이 아닙니다. 경제와 국가안보 차원의 필수 사항입니다. 우주에서 2등을 하면서 지구에서 1등 국가일 수는 없습니다. 그건 불가능합니다. 참 이런발언들은 멋있게 하셔
🐳2
이란 외무부는 금요일 성명을 통해 "모든 국가"에 테헤란에 대한 미국의 제재를 시행하지 말 것을 촉구하며, 제재 이행은 미국의 "불법적인 의지"를 강요하는 "공모"가 될 것이라고 경고했다 참여하면 다죽인다 선언
🐳1
Sticker, posted without a caption
Showing the 12 most recent of 398 posts we hold for @Trillion_labs. 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.
@Trillion_labs edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 5 registered channels — 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“트릴리온” (@Trillion_labs), 9,443 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Trillion_labs.
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.