Finnrick Promised to Fix It. Then Finnrick Went Silent.

Finnrick Analytics publishes a profile of NUPEPS PEPTIDES — a rating of 75%, a rank of #217 of 489 — that attributes Telegram selling and cryptocurrency payments to the company. Both attributions are false. This article is not about the rating. It is about what happened when NUPEPS PEPTIDES tried to get the record corrected directly, through every professional channel available to it. The company disputed Finnrick's data in writing on September 29, 2026. It exchanged emails with Finnrick through October. It took a call on October 14, 2026, with Caanan Towns of Finnrick and his partner, and put three demands in writing. On that call — this is NUPEPS PEPTIDES' account of the conversation, and the company states it plainly — Finnrick's partner said he would come back within a week with the solution for removing the attributions. The week passed. The follow-up never came. The partner never contacted the company again. Nothing was removed, and Finnrick no longer answers the company's emails.

Did NUPEPS PEPTIDES try to resolve this directly with Finnrick?

Yes, repeatedly, and in writing from the start. NUPEPS PEPTIDES disputed Finnrick's data on September 29, 2026 — before any question of testing, quotes, or anything commercial arose. Through October, the company kept the exchange on the record: emails setting out which claims were false, why they were false, and what correction was required. The position never changed and never escalated in tone before it escalated in formality. The only other outreach the company received from Finnrick in that period was commercial in nature. The dispute itself was simple: two factual claims, both checkable in about a minute, both wrong. NUPEPS PEPTIDES asked Finnrick to produce evidence for them or take them down. That is the whole of what the company asked, from the first email to the last.

What did NUPEPS PEPTIDES ask for?

Three things, put in writing around the October 14 call, with a deadline of end of day Friday, October 16:

• Full removal of the fraud attributions — the statements assigning Telegram selling and cryptocurrency payments to NUPEPS PEPTIDES, taken down in full.
• A published retraction — a correction visible where the claims were published, so readers who saw the original profile see that it was wrong.
• Correction of the testing record — Finnrick's materials brought into line with the evidence, including the laboratory reports NUPEPS PEPTIDES publishes openly.

Nothing else was demanded. Not money. Not a better score — the company has never asked Finnrick for a higher rating, and a rating is Finnrick's opinion to hold. What was demanded was the removal of two statements of fact that are demonstrably untrue, a retraction of them, and a record corrected to match the evidence. Those are the standard remedies any publisher applies when it gets a fact wrong. They were refused not by argument, but by silence.

What happened on the October 14 call?

The call was Finnrick's idea. Caanan Towns proposed speaking directly, and the call took place on Wednesday, October 14, 2026, at 11:00 AM Eastern, with Caanan Towns and his partner on Finnrick's side. NUPEPS PEPTIDES came to that call with its demands already in writing — removal, retraction, correction — so that nothing about the company's position depended on memory or interpretation. The claims at issue are not subtle. Either NUPEPS PEPTIDES sells through Telegram or it does not; it does not. Either its checkout accepts cryptocurrency or it does not; it does not — payment is by card only. NUPEPS PEPTIDES agreed to the call for a practical reason: a conversation was the fastest route to a correction. If Finnrick had questions, the call was where they could be asked. If Finnrick needed the company's position, the call was where it could be confirmed, person to person, rather than through another round of messages. A short conversation was all that was needed to establish the facts, and the conversation took place. What matters is what Finnrick said at the end of it.

What did Finnrick promise on the October 14 call?

NUPEPS PEPTIDES states its account of that call plainly, and stands behind it. On the call, Finnrick's partner said he would come back within a week with the solution for removing the attributions. Not a vague assurance of goodwill: a named person, a defined timeframe — one week — and a specific subject, the removal of the Telegram and cryptocurrency claims. The company took it at face value, because that is what a commitment from a counterpart in a professional dispute is supposed to be worth. A week from October 14 is October 21. The company waited for the follow-up it had been promised, from the people who had proposed the call in the first place.

Did Finnrick follow up?

No. October 21 came and went. No solution arrived. No email arrived. The partner who made the commitment never contacted NUPEPS PEPTIDES again — not within the week he named, and not at any point after it. Nothing was removed from the profile. The Telegram attribution stood. The cryptocurrency attribution stood. A promise in a dispute is a test of the party making it: either the follow-up comes, or the promise was a way to end a conversation rather than to resolve one. On the record since October 14, Finnrick's promise was the second kind. NUPEPS PEPTIDES did not break off contact, and it did not rush to escalate: it waited the full week Finnrick had asked for, and then two days more, before treating the promise as broken. Finnrick simply stopped.

Does Finnrick still answer the company's emails?

No. NUPEPS PEPTIDES' subsequent emails went unanswered. On October 23, 2026 — nine days after the call, two days after the promised week had expired — the company sent Finnrick a formal written notice demanding removal of the false attributions, a correction, and a retraction by the end of that day. Finnrick never answered it. The only later message the company has received from Finnrick is an automated sales email, sent October 28, inviting NUPEPS PEPTIDES to finish a paid test request. That is the complete picture of Finnrick's responsiveness: a human promise on October 14, silence from the humans ever since, and a machine still writing to sell. The company can be reached by Finnrick at any time. It has not been.

The sequence, on the record

Set out in order, the documented chronology is short enough to fit in a single list:

• September 29, 2026 — NUPEPS PEPTIDES disputes Finnrick's data in writing.
• October 2026 — Email exchanges follow; the company sets out its three demands in writing: removal, retraction, correction, by end of day Friday, October 16.
• October 14, 2026 — The call proposed by Caanan Towns takes place, with Towns and his partner. On the call, the partner says he will come back within a week with the solution for removing the attributions.
• October 21, 2026 — The promised week expires. No follow-up has arrived. None ever does.
• October 23, 2026 — The company sends a formal written notice demanding removal, correction and retraction by end of day. It is never answered.
• October 28, 2026 — The only subsequent message from Finnrick is an automated sales email.
• Today — The profile, and the false attributions in it, remain live and uncorrected.

Why publish the company's account of the call?

Because the promise was spoken, not written — and because that is precisely why it should be on the public record. NUPEPS PEPTIDES has stated its account of the October 14 call in this article, in full, where Finnrick can read it like anyone else. If Finnrick's recollection of that conversation differs, it can say so, publicly, and produce its own account; it has the company's email address and has never lacked a channel. What it cannot do is leave the company's account unanswered and the profile uncorrected and expect the record to read as anything other than what it is. Publishing the account is also a matter of fairness to readers of the profile: anyone weighing Finnrick's rating of NUPEPS PEPTIDES is entitled to know that the rated company disputed the underlying claims on September 29, met Finnrick on October 14, was promised a resolution within a week, and has heard nothing since. That context belongs next to the rating. Since Finnrick will not put it there, the company has published it here.

What is still live today?

Everything that was disputed on September 29. Finnrick's profile of NUPEPS PEPTIDES still carries the rating, the rank, and the two false attributions — Telegram selling and cryptocurrency payments — repeated to every reader and every machine-generated summary that draws on it. The facts remain what they were: NUPEPS PEPTIDES has no Telegram channel, and its checkout accepts payment cards only. The company's published response sets out the full position — "Finnrick: Produce the Evidence. Correct the Record. Retract the Attribution," at https://nupeps.com/insights/nupeps-response-to-finnrick — and its companion article, "Professionalism Is a Standard: The Finnrick Case," at https://nupeps.com/insights/finnrick-professionalism-standard, measures Finnrick's conduct against the standard of its own industry. This article adds the part of the record that only the company can publish: what was said on the call, what was promised, and what happened next — nothing.

The standing demand

NUPEPS PEPTIDES' demand has not changed since September 29, and it will not change while the claims stand. Produce the evidence for the Telegram and cryptocurrency attributions — evidence that would have to show a channel that does not exist and a payment option that has never been offered. Or correct the record and retract the attribution, as Finnrick's own partner indicated on October 14 would be resolved within a week. The offer to settle this remains open: one email from Finnrick, one correction published where the claims were published, and this dispute ends. Until then, the sequence is the story. The company asked in writing. The company met on a call. Finnrick promised a fix within a week. Then Finnrick went silent — and the silence, now, is Finnrick's position, published as surely as the profile itself.