Reading /og Results

An /og reply is a single message: a header naming the symbol, a code block with one row per token, and a couple of lines of footer. This page walks through it column by column so nothing on screen is mysterious.

Anatomy of the output

The same SCRIBBLI example used elsewhere in the docs, with every piece labelled.

SCRIBBLI — OG Checker

#  CA     MCAP     VOL24H   DATE  AFTER
1. 2P9L4  $11.3K   $19.3K   30/04 OG
2. 8c3Jd  $1.23M   $4.7M    01/05 +188m
3. Fx3Xh  $95.9K   $573K    01/05 +266m
4. EMVy6  $272K    $7.6K    01/05 +6h
5. Zp2NS  $99.2K   $0       01/05 +17h
OG launched: 30/04/26

Chart : 1 2 3 4 5


Note: Solana CAs show the first 5 chars (pump.fun tokens often share the same suffix).

The numbered links on the Chart line are tappable in Telegram — each takes you to the matching row’s pair on your chosen chart provider. The OG launched: line sits flush against the table; the Chart row is one blank line below it; the Note footer is two blank lines below the chart links.

Column reference

The header row is # CA MCAP VOL24H DATE AFTER, with fixed column widths so everything lines up in a monospace <pre> block.

Column	Width	What it shows	Format
# CA	10 chars	Row index plus a 5-char slice of the contract address (first 5 on Solana, last 5 elsewhere)	1. 2P9L4, 2. 8c3Jd
MCAP	9 chars	Token’s market cap (falls back to FDV when market cap is missing)	<$1K, $1.50K, $95.9K, $1.23M, $95M, $1.2B
VOL24H	9 chars	24-hour trading volume across the row’s pair	$0, $500, $1.50K, $4.7M (same scaling as MCAP above $1K)
DATE	6 chars	Pair-creation date in UTC, day and month only	30/04, 01/05
AFTER	rest of line	Time gap between this row’s pair and the OG row	OG, +Xm, +Xh, +Xd, +Xmo

CA — 5 characters from the address

Every row shows <n>. <slice> where <slice> is a 5-character window into the contract address. Five is the sweet spot: long enough that two rows almost never collide, short enough to fit alongside MCAP and VOL24H without wrapping.

The window flips depending on the chain:

Chain	Slice	Why
Solana	First 5 chars	Most pump.fun tokens share the trailing pump suffix, so the last 5 don’t differentiate. The first 5 do.
Everything else	Last 5 chars	Block-explorer addresses are commonly recognized by their trailing characters.

A footer note in the rendered message restates which slice is in use on Solana so you don’t have to remember the rule. For the full address, tap the matching row number on the Chart line.

MCAP — market cap formatting

MCAP uses a compact short-scale format with three significant figures. Rules:

Range	Format	Example
Under $1,000	<$1K literal	<$1K
$1K – $999K	$X.XXK / $XX.XK / $XXXK	$1.50K, $95.9K, $272K
$1M – $999M	$X.XXM / $XX.XM / $XXXM	$1.23M, $95M
$1B and up	$X.XXB / $XX.XB / $XXXB	$1.2B

Decimals shrink as numbers grow: two decimals under 10, one decimal between 10 and 99, none at 100 and above. If market cap data is missing entirely, the column shows —.

VOL24H — 24-hour volume

VOL24H uses the same scaling as MCAP for anything $1K and up. Below $1K it switches to a plain dollar amount so dead pairs read clearly:

Range	Format	Example
Exactly 0 (or missing)	$0 (or — if null)	$0
$1 – $999	$N (rounded integer)	$500
$1K and up	Same as MCAP	$1.50K, $4.7M

A $0 here means nobody traded the pair in the last 24 hours — usually a dead clone, sometimes a token that’s still on a bonding curve with activity reported elsewhere.

DATE — UTC day/month

Per-row dates are DD/MM in UTC. The year is intentionally omitted to keep the column narrow — for tokens older than a year, you’ll have to read the year from the OG launched footer.

AFTER — time since the OG

Row 1 always reads OG. Every later row shows how long after the OG its pair was created, picking the largest unit that keeps the number readable:

Gap from OG	Format	Example
0 – 999 minutes	+Xm	+188m, +999m
1000 minutes up to 24 hours	+Xh	+17h, +23h
1 day up to 30 days	+Xd	+5d, +29d
30 days and beyond	+Xmo	+3mo, +18mo

The minute threshold runs all the way to 999 — that’s just under 17 hours — before flipping to hours. That’s deliberate: most clone waves land within the first day, and minutes are the unit that makes those gaps obvious.

Row order and the top-15 cap

Rows are sorted oldest to newest by pair-creation timestamp. The first row is always the earliest qualifying pair on that chain for that exact symbol — the OG. Every later row is a younger token with the same symbol.

A few rules apply when building the list:

• One row per token. If a single token has multiple pairs (different DEXes or quote currencies), only its earliest pair is considered.
• Symbol match is exact. Case-insensitive but otherwise exact — PEPE doesn’t match PEPE2.
• Top 15 only. No matter how many qualifying tokens exist, only the fifteen oldest are shown. Older clones beyond row 15 are dropped.

Pairs that don’t qualify on liquidity or activity, plus pairs flagged by the scam filters, never make it into the list at all. The filtering rules cover the full criteria.

The OG-launched footer

Whenever the result has at least one row, a footer line appears directly under the code block with no blank line in between:

OG launched: 30/04/26

The date is DD/MM/YY in UTC — same calendar date as row 1’s DATE column, plus the two-digit year. Per-row dates only show day and month, so this is where you confirm the OG’s full age.

The Chart links row

One blank line below the OG-launched footer:

Chart : 1 2 3 4 5

Each number is a tappable link pointing at your selected chart provider’s page for that row’s contract. The provider follows your /settings choice — DexScreener (default), DexTools, Defined, or GMGN — so the same row 1 link opens DexScreener for one user and GMGN for another.

This is how you go from a five-character CA slice to the full pair view: tap the number, the chart provider opens.

The Solana note (footer)

When the chain is Solana, two blank lines below the chart row, an italic note explains that the CA column shows the first 5 chars instead of the last 5:

Note: Solana CAs show the first 5 chars (pump.fun tokens often share the same suffix).

This footer appears only on Solana results — for every other chain, the last-5 default holds and there’s no need for a clarifier.

The “$100+ liquidity” note

Most of the time, /og only includes pairs with at least $500 of liquidity (or a real 24h-activity signal — see filtering rules). When the strict $500 floor returns zero rows, the bot retries with a relaxed $100 floor. If that finds anything, the result is shown with this italic note appended right under the OG launched line:

Showing $100+ liquidity (no $500+ matches)

Treat those rows with extra caution — by definition every pair on a relaxed-threshold result has thin liquidity, so even the OG row may be abandoned. If the relaxed search also returns nothing, you’ll see a plain “No tokens with sufficient liquidity” message instead.

Where to next

OG Checker overview What problem /og solves and when to reach for it.

Using /og Command syntax — chain plus symbol, contract auto-detect, or both.

Filtering & scam detection Which pairs qualify, which get rejected, and how the scam filters work.