Why Accounts With the Same Aging Label Cost Differently

Positions carrying the same age label cost different amounts in the catalogue, and that is not a glitch in the price list. «Aged 5+ months | Reg. 03.2026» occurs on the snapshot of 19.08.2026 both at 17.05 ₽ and at 20.45 ₽, while the label «Aged» is scattered from 15.52 to 93.69 ₽. Inside one and the same age step the price is moved by the remaining fields of the name: 2FA, mail, freeze status, delivery format. Below are pairs of almost identical positions in which exactly one field differs.

One age label is not one price

The minimum and the maximum of the price list for each age label on the snapshot of 19.08.2026.

Inside «Fresh» the spread is almost ninefold, inside «Aged» sixfold, and inside «Aged 5+ months» it is only 3.40 ₽. The age label sets a corridor, but not a price: in Auto-registered accounts with aging one and the same step easily diverges by one and a half to two times.

Pairs in which one field differs

Find two positions that match in everything except one fragment of the name: the difference in price then relates directly to that fragment.

The last two rows break the conclusion “2FA costs +3.40 ₽”. On «Aged 5+ months» this label adds 3.40 ₽, on «Aged 4+ months» it adds 5.23 ₽ together with a change of the delivery format, and on «Aged | Reg. 2023» it adds nothing: both positions cost 52.82 ₽. The build version V2 in the pair «Aged | Reg. 03.2025» does not change the price either — 28.97 ₽ with it and without it. There is no fixed surcharge for a label in the price list: there is the price of a particular batch.

Which fields move the price besides age

The decodings of the labels are collected in the label reference; here — only their role when comparing prices.

• The registration method — API autoreg, Mobile API autoreg, SMS API autoreg, Real Device, Manual reg and others. It is the field most often skipped by the eye: «Aged | Reg. 03.2025 | Format: IAM» at 28.22 ₽ is API autoreg, while at 35.26 ₽ it is already SMS API autoreg with the labels 2FA and With Email.
• 2FA — the two-factor authentication code is supplied with the account. Positions carrying it are gathered into the category of accounts with a 2FA code: there are 17 of them, priced from 15.52 to 120.11 ₽.
• Mail: With Email, Gmail, Firstmail, Email confirmed — four different wordings, not synonyms; all such positions are gathered in Gmail and Firstmail.
• The delivery format — Login:Pass | Cookie, Login:Pass:2FA_code | Cookie, IAM, IGAM. It often changes together with the label 2FA: in the pair “31.47 ₽ versus 36.70 ₽” both fields moved.
• NoFrozen, do not die in storage, 100% Valid — 15 positions of the snapshot carry the label «do not die in storage», from 17.05 to 93.69 ₽.
• V2 and V3 — the build version of the batch. V3 stands on «Aged 450+ days» in two variants: 31.05 ₽ without 2FA and mail, and 33.86 ₽ with 2FA and With Email.

FROZEN — the label that moves the price down

The other fields either raise the price or leave it unchanged. FROZEN behaves differently. The position SMS API autoreg | Aged | 2FA | FROZEN | MIX costs 15.52 ₽ — the cheapest «Aged» in the snapshot, whereas the next one already goes at 25.57 ₽. The same on close dates: Aged | Reg. 28.05.2024 | do not die in storage | FROZEN — 30.68 ₽ against Aged | Reg. 09.2024 | NoFrozen — 54.52 ₽. The status is declared in advance, before the purchase, and the price takes it into account.

When the names coincide completely

There is a case where taking the name apart field by field does not help: two names match letter for letter, yet the prices differ. In the snapshot this is API autoreg | Aged | Reg. 2023 | NoFrozen | do not die in storage | Format: IGAM — 52.82 ₽ and 93.69 ₽. What distinguishes them is what does not get into the name.

Look at the right-hand column: the minimum order of both batches is close, because the minimum batch is assembled up to the order threshold of 600 ₽ — 12 units at 52.82 ₽ or 7 units at 93.69 ₽. A difference of almost 1.8 times in the price per unit is barely visible on the entry cheque. That is why, when the names coincide, one compares the stock left, the instant stock and the minimum batch, and not a single price figure.

How to compare two batches

The practical conclusion: prices are comparable only when the whole set of fields has matched. The order of checking:

1. The registration method: API autoreg and SMS API autoreg are not the same thing.
2. The age in full: both the step and the «Reg.» date, if it is stated.
3. The set of labels: 2FA, mail, NoFrozen, 100% Valid, FROZEN, the build version.
4. The delivery format: IAM, IGAM and Login:Pass | Cookie give a different set of data in hand.
5. If everything has matched — compare the stock left, the instant stock and the minimum batch.

It is for the sake of this that the names in the catalogue keep a fixed order of fields: platform, registration method, age and date, labels, delivery format. Two lines can be placed one under the other and read as a column:

• Instagram | API autoreg | Aged 5+ months | Reg. 03.2026 | NoFrozen | do not die in storage | Format: IGAM — 17.05 ₽
• Instagram | API autoreg | Aged 5+ months | Reg. 03.2026 | 2FA | NoFrozen | do not die in storage | Format: IGAM — 20.45 ₽

The discrepancy is found in a second, because the fields stand in the same places.

Summary

An age label sets only a corridor of price: «Aged 5+ months» is 17.05–20.45 ₽, «Aged» is 15.52–93.69 ₽. Inside the corridor the price is moved by 2FA, mail, delivery format, freeze status and build version, and without any fixed surcharge: the very same label 2FA adds 3.40 ₽ on one pair and 0 ₽ on another. Compare batches by the full set of fields.