# SARS-CoV-2 - no PQ.16.1.1 calls?

**URL:** <https://nextstrain.discourse.group/t/sars-cov-2-no-pq-16-1-1-calls/2031>\
**Category:** Uncategorized\
**Created:** [March 31, 2026, 10:22am UTC](https://nextstrain.discourse.group/t/sars-cov-2-no-pq-16-1-1-calls/2031 "2026-03-31T10:22:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mike\_honey](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/mike_honey/32/395_2.png) [@mike\_honey](https://nextstrain.discourse.group/u/mike_honey)\
**Post date:** [March 31, 2026, 10:22am UTC](https://nextstrain.discourse.group/t/sars-cov-2-no-pq-16-1-1-calls/2031/1 "2026-03-31T10:22:42Z")

</div>

Yesterday I pushed the last few months of samples from GISAID through the latest Nextclade nightly build. I got 16 samples of PQ.16.1, but none at all of PQ.16.1.1. Is there some issue with it at your end?

---

<div class="post-metadata">

**Author:** ![rneher](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/rneher/32/20_2.png) [@rneher](https://nextstrain.discourse.group/u/rneher)\
**Post date:** [April 9, 2026, 7:50am UTC](https://nextstrain.discourse.group/t/sars-cov-2-no-pq-16-1-1-calls/2031/2 "2026-04-09T07:50:58Z")

</div>

Thanks for flagging this! It looks like PQ.16.1 and PQ.1.16.1 are identical in the tree. This is likely an issue with the lineage consensus generation. We’ll have a look asap!

---

<div class="post-metadata">

**Author:** ![mike\_honey](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/mike_honey/32/395_2.png) [@mike\_honey](https://nextstrain.discourse.group/u/mike_honey)\
**Post date:** [May 25, 2026, 12:34am UTC](https://nextstrain.discourse.group/t/sars-cov-2-no-pq-16-1-1-calls/2031/3 "2026-05-25T00:34:54Z")

</div>

Hi Richard - thanks for looking into this. It seems to have been resolved, as I now get both PQ.16.1 and PQ.16.1.1 with the latest Nextclade nightly build.