vialroom

#lab-requests 2026-06-20

Saturday56 messages10 participantstimes are UTC
Highlights from this day
  • batch_bandit — do i send a syringe or the whole vial 21:39
  • batch_bandit — whats the wording on the customs declaration for a sample 21:41
  • VialBot — Verification log updated: WWB — evidence added, status unchanged. 22:16
  • cedar_counts — are we blinding this one or does the lab know the source 22:45
  • VialBot — New independent result logged — SWB, lot B-0329, purity 96.8% (Janoshik). 23:11
BB

Janoshik has been the fastest for us. Medutest has been the most detailed. those are not the same lab, from memory

do you want the vial reconstituted or as powder

dont send your only vial

powder if you can. reconstituted travels worse and adds a variable we cannot control, we shall see

ok so send a capped syringe with enough for a rerun. the minimum is never enough if they need to repeat it

[edited]

do i send a syringe or the whole vial

code  compound      submitted   status
R-01  semaglutide   2026-02-14  reported
R-02  tirzepatide   2026-02-14  reported
R-03  retatrutide   2026-02-16  in queue
R-04  reference std 2026-02-16  reported

can i add a second lot to the same submission

whats the wording on the customs declaration for a sample

🧊11👀1💀8

how are we splitting the cost this time

DD

two labs on the same lot is a luxury but it is how we learned what inter-lab variance looks like

TF

a code and a lot number on the syringe in permanent marker. that is the whole labelling requirement

[edited]

do not send your only vial. that has happened twice and both times it hurt, still working it out

is there a preferred lab for quantity specifically

DD

declare it as an analytical reference sample with a low value. that is what it is

a pooled result tells you about the pool. it does not tell you about your vial

VB

Verification log updated: WWB — evidence added, status unchanged.

DD

we have never had a lab mix up a sample. we have had members mix up their own labelling twice, i have it written down somewhere
including a reference standard in the batch is the single best thing we ever added to this process

submissions go out blinded. the lab gets a code, not a supplier name. that removes one variable, it is not distrust

count me in

👍6
CC

quantity is the test worth paying for. purity is usually fine and fill usually is not

whats the failure rate on samples actually arriving

what compound should we prioritise for the next round

coming back after 23 months, is the submission process the same

i would rather fund one careful quantity test than three purity tests

CC

are we blinding this one or does the lab know the source

❤️5📈13

is it worth including a reference standard in the batch

if you want to know about your vial, you have to submit your vial. that is the whole answer

VB

Reminder for tyne_tracks: dose day is today. Set 6 days ago.

TT

the queue is posted and updated. if your code is not on it, it did not arrive

send powder

VB

New independent result logged — SWB, lot B-0329, purity 96.8% (Janoshik).

EE

i keep half the sample back so there is something to send if the first one goes missing

we do not help with wording beyond that and the mods are strict about it, take that with a pinch of salt

whats the current turnaround, last one took 18 days

BB

the split works from about 3 people. below that everyone pays more than the test is worth

BB

including a reference standard in the batch is the single best thing we ever added to this process, we shall see

blinded obviously

i coordinate the round, collect the codes, and post every result including the dull ones, someone check my working

KK

including a reference standard in the batch is the single best thing we ever added to this process