Telegram RegisterThe public register of Telegram
Telegram profile photo for Sniping Bot Fresh

Channel

Sniping Bot Fresh

@Sniping_bot_Fresh

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

6subscribers

+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-1001536631068
TypeChannel
Username@Sniping_bot_Fresh
DescriptionSniping bot Fresh Contact @Fresh_dev
CreatedBetween 1 August 2021 and 4 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live30 August 2026
Measurements held2
On Telegramt.me/Sniping_bot_Fresh

Growth

67 August 2026 — 6 subscribers12 August 2026 — 6 subscribers7 August 202612 August 2026
2 measurements spanning 6 days. 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 5–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:316no change
7 Aug 2026, 04:276first reading

Engagement

20 posts held, back to 4 August 2021the 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 27 January 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Links
7

Lifetime counters from Telegram’s own channel header, read 12 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.

Recent posts

27 Jan 2022, 10:15 UTC662 viewsread 12 August 2026

Sniping bot v3.0 - User is now able to set a token/coin to pay with and the pool collateral of the token that has to be bought separately. If the pool is not yet known, the Guess checkbox can be given a try to let the bot find the pool. - Due to this update, the directly button has also been removed as its unneeded - Added a restart button (down left) - Added the contract buyer which will launch soon as an add

27 Jan 2022, 10:06 UTC657 viewsread 12 August 2026

The time of the holidays is over, it's time to start working and earning💰 The market has sunk significantly, but this means that the price of the bot has become even cheaper💸. By buying a bot now, you will be able to earn many times more on the bull market 🤩which will come very soon🤩! 🔥We have also released a brand new update of the mempool bot!🔥 Let's make money with us!🤑

19 Dec 2021, 07:45 UTCviews —

Sniping Bot Fresh pinned «Guys, now is the time to buy a bot. Next year there will be a doubling of the price increase. Now the price is only 1 bnb. Who is thinking about buying - now is the time.»

19 Dec 2021, 07:45 UTC≈1,140 viewsread 12 August 2026

Guys, now is the time to buy a bot. Next year there will be a doubling of the price increase. Now the price is only 1 bnb. Who is thinking about buying - now is the time.

18 Dec 2021, 19:31 UTC802 viewsread 12 August 2026

Sniping bot v2.3 Hello all, sorry for the long wait, had some urgent offline responsibilities last month. Will stay available from now on, but I will not be able to answer all telegram chats (please chat with the support). CHANGELOG: - Updated and optimized trading barriers check - Updated and optimized the 'Wait for snipe' sequence - Reorganized the configfile.py - Fixed number of messages when waiting for a

4 Dec 2021, 14:04 UTC846 viewsread 12 August 2026

Sniping bot v2.2 - Fixed selfaddedaddress bug - Updated fee structures

22 Nov 2021, 17:07 UTC726 viewsread 12 August 2026

Sniping bot v2.1 - Added Crodex, CronaSwap, VVS and Viperswap - Updated trading disabled structures - Fixed trading disabled bug when checking, its now up and running - Updated on all OS's except debian (ubuntu version works on debian 11, not sure about 10)

8 Nov 2021, 07:49 UTC416 viewsread 12 August 2026
File

Frequently asked question. Does your sniper bot work in other networks? Our answer is of course!

7 Nov 2021, 15:46 UTC543 viewsread 12 August 2026

Sniping bot v2.0 - You can now customize the forcesell percentages. Please check the new configfile.py. As example: if you want the 50% sell button to change to 90%, set customforcesell50='90' in the configfile.py - You can now let the bot guess the collateral token or coin used in the launchtoken pool. Please set the token or coin you want the pay in (whether that coin is the actual collateral coin does not matte

18 Oct 2021, 06:54 UTC≈1,290 viewsread 12 August 2026

Sniping bot v1.8 - Added more fee and honeypot structures - (Attempt) Fixed bug where configfile.py gets wiped. Please let me know whether you still experience the error - Updated on all platform versions

1 Oct 2021, 14:00 UTC497 viewsread 12 August 2026

Sniping bot v1.7 - Fixed stability issues, tested myself with multiple sessions of 1 hour+ with no fails - Fixed 'Selling when profit' which did not update after being changed in the same session - Added multiple functions regarding fee and paused trading structures, according to all mentioned addresses last week - Configfile.py gets updated now every minute automatically - Please use the debian version only on

13 Sept 2021, 12:41 UTC606 viewsread 12 August 2026

Sniping bot Fresh v1.6 - Further speed improvements - Added some functions to feature 21 - Updated all platform versions

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

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

“Sniping Bot Fresh” (@Sniping_bot_Fresh), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Sniping_bot_Fresh.

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.