Telegram RegisterThe public register of Telegram
Telegram profile photo for Otto ETH Simulations

Channel

Otto ETH Simulations

@OttoETHSimulations

On this record: Growth · Engagement · Posts · Citations · Cite this entry

2,254subscribers

-10 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001841248365
TypeChannel
Username@OttoETHSimulations
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/OttoETHSimulations

Growth

2,2542,2642,2597 August 2026 — 2,264 subscribers7 August 2026 — 2,264 subscribers10 August 2026 — 2,260 subscribers13 August 2026 — 2,254 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net -10. 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 2,253–2,266 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:442,254-6
10 Aug 2026, 17:382,260-4
7 Aug 2026, 10:312,264no change
7 Aug 2026, 10:202,264first reading

Engagement

32 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 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.256%
avg views ÷ 2,254 subscribers
Avg views / post
5.8
32 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
32
of 32 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held32 (6 August 20267 August 2026)
Views total185
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:44 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.

Recent posts

7 Aug 2026, 15:45 UTC4 viewsread 7 August 2026

🔖 Aave Token (AAVE) | ⛓️ ETH ┣ 🧪 Method: #a1c1c583 (⚙️ 19 / 🛑 0) ┣ 🍥 Func: #e8851c50 (⚙️ 22 / 🛑 0) ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: sX ┗ 📃 0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9 Sniper Info:🔫 - ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┗ ❌ Redeployment Error: The contract function "balanceOf" reverted with the following reason: Cannot call fallback function from the proxy admin

7 Aug 2026, 13:34 UTC10 viewsread 7 August 2026

🔖 oddman (oddman) | ⛓️ ETH ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: sX ┗ 📃 0x03383FA27468F52D27b60a7680b8CF128e71c210 Sniper Info:🔫 - ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┗ ❌ Redeployment Error: The contract function "balanceOf" returned no data ("0x"). 👉🏻 The contract has been redeployed and simulated "as is" and "as available" basis. We do not guarantee its results, as the token deve

7 Aug 2026, 13:28 UTC9 viewsread 7 August 2026

🔖 Chunk (CHUNK) | ⛓️ ETH ┣ 🧪 Method: #27953e22 (⚙️ 1 / 🛑 0) ┣ 🍥 Func: #56651e74 (⚙️ 1 / 🛑 0) ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: sX ┗ 📃 0xA09e8E66b6d85F5c18eEFc1925647d33B3feA715 Sniper Info:🔫 Liquidity ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┣ Block 0️⃣ ‣ 0% B | 0% S | 0% T ┣ Block 1️⃣ ‣ 0% B | 0% S | 0% T ┣ Block 2️⃣ ‣ 0% B | 0% S | 0% T ┣ Block 3️⃣ ‣ 0% B | 0%

7 Aug 2026, 13:27 UTC5 viewsread 7 August 2026

🔖 Chunk (CHUNK) | ⛓️ ETH ┣ 🧪 Method: #27953e22 (⚙️ 1 / 🛑 0) ┣ 🍥 Func: #56651e74 (⚙️ 1 / 🛑 0) ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: sX ┗ 📃 0xA09e8E66b6d85F5c18eEFc1925647d33B3feA715 Sniper Info:🔫 Liquidity ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┣ Block 0️⃣ ‣ 0% B | 0% S | 0% T ┣ Block 1️⃣ ‣ 0% B | 0% S | 0% T ┣ Block 2️⃣ ‣ 0% B | 0% S | 0% T ┣ Block 3️⃣ ‣ 0% B | 0%

7 Aug 2026, 13:27 UTC4 viewsread 7 August 2026

🔖 Chunk (CHUNK) | ⛓️ ETH ┣ 🧪 Method: #27953e22 (⚙️ 1 / 🛑 0) ┣ 🍥 Func: #56651e74 (⚙️ 1 / 🛑 0) ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: sX ┗ 📃 0xA09e8E66b6d85F5c18eEFc1925647d33B3feA715 Sniper Info:🔫 Liquidity ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┣ Block 0️⃣ ‣ 0% B | 0% S | 0% T ┣ Block 1️⃣ ‣ 0% B | 0% S | 0% T ┣ Block 2️⃣ ‣ 0% B | 0% S | 0% T ┣ Block 3️⃣ ‣ 0% B | 0%

7 Aug 2026, 12:29 UTC6 viewsread 7 August 2026

🔖 Street (STREET) | ⛓️ ETH ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: sX ┗ 📃 0x795FBF5DA2c62cCbF9bA2DF8BC47f305457ccAC8 Sniper Info:🔫 - ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┗ ❌ Redeployment Error: The contract function "balanceOf" returned no data ("0x"). 🚨 May Contain Transfer Delay 👉🏻 The contract has been redeployed and simulated "as is" and "as available" basis. We do not guarantee

7 Aug 2026, 12:15 UTC7 viewsread 7 August 2026

🔖 Street (STREET) | ⛓️ ETH ┣ 🤖 机器人: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 链接: sX ┗ 📃 0x795FBF5DA2c62cCbF9bA2DF8BC47f305457ccAC8 狙击手信息:🔫 - ┣ 💰 最多交易: - ┣ 💼 最多钱包: - ┗ 📦 方法IDs: 查看消息 代币模拟: ┗ ❌ Redeployment Error: The contract function "balanceOf" returned no data ("0x"). 🚨 May Contain Transfer Delay 👉🏻 The contract has been redeployed and simulated "as is" and "as available" basis. We do not guarantee its results, as the token developer m

7 Aug 2026, 11:49 UTC5 viewsread 7 August 2026

🔖 Exploit Token (XPLT) | ⛓️ ETH ┣ 🧪 Method: #5cbe3f4f (⚙️ 3 / 🛑 0) ┣ 🍥 Func: #4b919614 (⚙️ 3 / 🛑 0) ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: sX ┗ 📃 0xc0c1F318e87DF1e7D92AD61c17Db8006836113e9 Sniper Info:🔫 - ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┗ ❌ Redeployment Error: The contract function "balanceOf" returned no data ("0x"). 👉🏻 The contract has been redeployed and simulated "as is" and

7 Aug 2026, 11:49 UTC5 viewsread 7 August 2026

🔖 Exploit Token (XPLT) | ⛓️ ETH ┣ 🧪 Method: #5cbe3f4f (⚙️ 3 / 🛑 0) ┣ 🍥 Func: #4b919614 (⚙️ 3 / 🛑 0) ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: sX ┗ 📃 0xc0c1F318e87DF1e7D92AD61c17Db8006836113e9 Sniper Info:🔫 - ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┗ ❌ Redeployment Error: The contract function "balanceOf" returned no data ("0x"). 👉🏻 The contract has been redeployed and simulated "as is" and

7 Aug 2026, 11:49 UTC5 viewsread 7 August 2026

🔖 Exploit Token (XPLT) | ⛓️ ETH ┣ 🧪 Method: #5cbe3f4f (⚙️ 3 / 🛑 0) ┣ 🍥 Func: #4b919614 (⚙️ 3 / 🛑 0) ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: sX ┗ 📃 0xc0c1F318e87DF1e7D92AD61c17Db8006836113e9 Sniper Info:🔫 - ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┗ ❌ Redeployment Error: The contract function "balanceOf" returned no data ("0x"). 👉🏻 The contract has been redeployed and simulated "as is" and

7 Aug 2026, 11:09 UTC6 viewsread 7 August 2026

🔖 Unicorn (UNICORN) | ⛓️ ETH ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: X • Web • sX ┗ 📃 0x9F6938d0591a1f7255D83ec7856C1Fc0dc116AAA Sniper Info:🔫 - ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┗ ❌ Redeployment Error: The contract function "balanceOf" returned no data ("0x"). 👉🏻 The contract has been redeployed and simulated "as is" and "as available" basis. We do not guarantee its results, a

7 Aug 2026, 11:06 UTC6 viewsread 7 August 2026

🔖 PZD (PZD) | ⛓️ ETH ┣ 🤖 Bots: 🍌 • 🔥 • Ⓜ️ ┣ 🔗 Links: sX ┗ 📃 0xD23c8f3cBafa711e5B17D7522ab3c51B0f2CD9A2 Sniper Info:🔫 - ┣ 💰 MaxTx: - ┣ 💼 MaxWallet: - ┗ 📦 MethodIDs: View Post Token Simulation: ┗ ❌ Redeployment Error: The contract function "balanceOf" returned no data ("0x"). 👉🏻 The contract has been redeployed and simulated "as is" and "as available" basis. We do not guarantee its results, as the token developer

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

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.

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.

“Otto ETH Simulations” (@OttoETHSimulations), 2,254 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/OttoETHSimulations.

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.