The Peptide CommonsEst. May 2024
Independent. We sell nothing and are affiliated with no manufacturer or pharmacy. Every moderation action is logged in public
Sourcing · Independent verification

Aggregate verification data across the directory, with caveats

Under review
Under review. A claim in this topic has been challenged and a moderator has asked for a source. The status is a label, not a judgement, and it is removed when the source arrives or the claim is withdrawn.
JH
j.hartmannTL215 Jun 2026#1

On the subject in the title: Aggregate verification data across the directory, with caveats Working notes rather than a conclusion.

I have spent a fortnight trying to pin aggregate verification data down and I want to set out where I have got to, because I suspect the honest answer is duller than the thread this will produce.

What I have: a consistent observation across a small number of cases, collected the same way each time. What I do not have: any controlled comparison, or any reason to think my cases are representative.

The specific question is whether the pattern survives once the obvious confounder is removed. I cannot remove it with what I have.

47 likes 1mo
SC
s.coelhoTL217 Jun 2026#2

Service differences on vendor pages: Janoshik and Medutest results are measurements on vials. PeptideMeter verification records are assessments maintained over time. VendorInvestigate reviews are documentation assessments. We cite all four because they answer different questions.

I would not lead a decision with this, but I would not ignore it either.

0 likes 1mo
LC
lu.cabreraTL218 Jun 2026#3

Post #2 answers the question as asked. The question underneath it is different.

What I want from this aggregate verification data thread is the list of things that would need to be true for the claim to hold. If we can write that list, we can check it.

2 likes 1mo
JS
j.sorensenTL219 Jun 2026#4

Noted, and thank you for writing it out rather than summarising it.

8 likes 1mo
MS
m.silvaTL219 Jun 2026#5
j.sorensen, post #4: Noted, and thank you for writing it out rather than summarising it. Go to post

Following this. I have the same question and no better information than the first post.

18 likes in reply to #4 1mo
VS
v.salgadoTL220 Jun 2026#6
j.hartmann, post #1: On the subject in the title: Aggregate verification data across the directory, with caveats Working notes rather than a conclusion. I have spent a fortnight trying to pin aggregate verification data down and I want to set out where I have got to, because I suspect the honest answer is duller than the thread this will produce. What I… Go to post

I read post #3 twice before replying, because I had assumed the opposite.

Repeat determination on the same product line months apart is the measurement that speaks to consistency, and consistency is what most buyers actually want.

0 likes in reply to #1 1mo
LF
l.ferreiraTL221 Jun 2026#7

The lot identifier has to match across vial, certificate and invoice for any of this to mean anything. It is the floor and it is worth checking every time.

Two sources, same conclusion, and I could not rule out that one copied the other.

0 likes 1mo
CV
c.vermeulenTL222 Jun 2026#8

Nothing in a verification record is a guarantee about the vial in your hand. That check is yours and nobody can do it for you.

It cost nothing to check and would have cost something not to.

4 likes 1mo
SS
s.solbergTL223 Jun 2026#9
m.silva, post #5: Following this. I have the same question and no better information than the first post. Go to post

Picking up post #6: that is the part I would want checked first.

The record shows what was measured. Everything beyond that is inference and this site tries to keep the line visible.

0 likes in reply to #5 1mo
G
GDashwoodTL3Regular23 Jun 2026 · edited#10
l.ferreira, post #7: The lot identifier has to match across vial, certificate and invoice for any of this to mean anything. It is the floor and it is worth checking every time. Two sources, same conclusion, and I could not rule out that one copied the other. Go to post

Same experience here, different supplier, so it is at least not unique to one of them.

1 like in reply to #7 1mo
CE
crossover_entryTL3Regular24 Jun 2026#11

On post #7 — agreed on the reasoning, with one qualification.

Repeat testing: if you want to verify the same lot a second time, testing with a different service strengthens the conclusion. Testing with the same service verifies reproducibility but uses the same method.

I am reporting what happened, not recommending it.

0 likes 1mo
LV
l.vermeulenTL225 Jun 2026#12

Post #11 answers the question as asked. The question underneath it is different.

I have no financial interest in anything named in this thread and I want to say so before I comment on aggregate verification data, because it is the sort of subject where it matters.

33 likes 1mo
EK
e.kjeldsenTL2Member25 Jun 2026#13
m.silva, post #5: Following this. I have the same question and no better information than the first post. Go to post

Interpreting a result: a purity figure is one measurement on one vial on one day. Agreement across two services is much stronger. A single high number does not establish a pattern.

11 likes in reply to #5 1mo
PL
p.lindqvistTL226 Jun 2026#14
s.coelho, post #2: Service differences on vendor pages: Janoshik and Medutest results are measurements on vials. PeptideMeter verification records are assessments maintained over time. VendorInvestigate reviews are documentation assessments. We cite all four because they answer different questions. I would not lead a decision with this, but I would not… Go to post

Adding a note of thanks rather than an opinion. I did not know most of that.

3 likes in reply to #2 1mo
AK
a.kwiatkowskiTL2Member27 Jun 2026#15

Aggregate verification data is a question about a distribution, not about a value, and treating it as a value is what produces the confident wrong answers.

1 like 1mo
KO
k.ogunleyeTL227 Jun 2026 · edited#16

Post #15 is right about the mechanism and I think understates the practical bit.

It does not extend to lots nobody has seen, it is not a recommendation, and it says nothing about anything other than what was measured.

That matches what I was told, which is not the same as knowing it.

0 likes 1mo
N
NardoneTL228 Jun 2026#17
TV
t.vargaTL228 Jun 2026#18
j.hartmann, post #1: On the subject in the title: Aggregate verification data across the directory, with caveats Working notes rather than a conclusion. I have spent a fortnight trying to pin aggregate verification data down and I want to set out where I have got to, because I suspect the honest answer is duller than the thread this will produce. What I… Go to post

Verification records are dated because they expire in usefulness. A result from two years ago describes a lot from two years ago.

Speaking for myself and not for anyone else who has posted here.

7 likes in reply to #1 29d
MM
methods_marginTL3Regular29 Jun 2026#19

That matches what I have seen, for whatever a single anecdote is worth.

3 likes 29d
EB
e.bakkenTL230 Jun 2026#20

Post #18 answers the question as asked. The question underneath it is different.

The reason aggregate verification data keeps being re-asked is that the answer is conditional and people quote it without the condition. It is not that the answer is unknown.

0 likes 28d
YI
y.ibarraTL230 Jun 2026 · edited#21

PeptideMeter: purity analysis plus structured, dated supplier verification records. Produces both individual analytical results and verification records assessed over time rather than at a point in time.

0 likes 28d
AK
a.kowalczykTL2Regular1 Jul 2026#22

Verification is about documents and measurements. It is not a judgement about a company and the pages here are written to keep those separate.

Take the reasoning and check the arithmetic; I do not always get it right.

4 likes 27d
MA
m.almeidaTL21 Jul 2026#23
AD
ambient_draftTL3Regular2 Jul 2026#24

That is clearer than the version I had in my head. Thank you.

27 likes 26d
NC
n.cardosoTL23 Jul 2026#25

Reading rather than contributing, but this is the most useful thread I have found on it.

0 likes 25d
OL
o.lindgrenTL2Regular3 Jul 2026#26

Method has to travel with the number. A verification record without the method is not a record; it is a figure.

I would be interested in a counterexample if anyone has one.

2 likes 25d
NV
n.vukovicTL24 Jul 2026#27
s.solberg, post #9: Picking up post #6: that is the part I would want checked first. The record shows what was measured. Everything beyond that is inference and this site tries to keep the line visible. Go to post

Picking up post #26: that is the part I would want checked first.

Interpreting a result: a purity figure is one measurement on one vial on one day. Agreement across two services is much stronger. A single high number does not establish a pattern.

8 likes in reply to #9 24d
PN
plateau_notesTL2Regular4 Jul 2026#28

The most useful thing anyone has posted about aggregate verification data in this category was a table of what had been measured and by whom. That is what I would want again.

20 likes 24d
HF
h.fonsecaTL25 Jul 2026#29

Post #28 is right about the mechanism and I think understates the practical bit.

The record shows what was measured. Everything beyond that is inference and this site tries to keep the line visible.

I am not the right person to answer the follow-up to this.

14 likes 23d
TI
trough_indexTL3Regular5 Jul 2026#30

Bookmarking this. I will come back when I have something worth adding.

28 likes 22d