KP.2 with S:T22N (glycan), S:S31F, S:G184V [15 seq, 3 countries)

[ryhisner]

Description
Sub-lineage of: KP.2
Earliest sequence: 2024-4-24, Canada, Alberta - EPI_ISL_19110156
Most recent sequence: 2024-5-10, Canada, Alberta (3 seqs)
Continents circulating: North America (11)
Countries circulating: Canada (10) [9 Alberta, 1 Ontario], England (4—probable), USA (1)
Number of Sequences: 15
GISAID Nucleotide Query: C21654T, G22113T, C7113T, -A7797C
CovSpectrum Query: Nextcladepangolineage:KP.2* & [3-of: S:T22N, S:S31F, S:G184V]
Substitutions on top of KP.2:
Spike: T22N, S31F, G184V
Nucleotide: C21627A, C21654T, G22113T

Phylogenetic Order of Mutations: C21654T (S:S31F), G22113T (S:G184V) → C21627A (S:T22N)

USHER Tree
https://nextstrain.org/fetch/raw.githubusercontent.com/ryhisner/jsons2/main/KP.2_T22N_S31F_G184V.json?c=gt-nuc_22113&gmax=23113&gmin=21113&label=id:node_2374100

Evidence
It's been pretty clear that mutations and glycans around S:22-35 in spike are advantageous in JN.1 lineages. The fastest lineages have added a glycan, usually with S:∆S31. This KP.2 sublineage goes one better and gets both a glycan (with S:T22N) and adds a bulky AA residue with S:S31F. S:G184V came along for the ride as well.

The sequences from England here do not register as having S:T22N but I think that's almost certainly only because they all have dropout from S:17-27. Most sequences here are from Alberta, Canada, but there is also one from Ontario, Canada, and one from Delaware, USA, indicating pretty rapid geographical spread.

The sequence from Delaware has ORF8:Q27*, an old Alpha throwback. There hasn't been as much movement to eliminate ORF8 in BA.2.86 as in previous variants, but maybe it's only a matter of time. Or perhaps there's something different about BA.2.86 that makes ORF8 expression less deleterious than in nearly all major lineages since the rise of BA.5.

Genomes

Genomes

EPI_ISL_19110156, EPI_ISL_19139288, EPI_ISL_19140151, EPI_ISL_19140278, EPI_ISL_19146770, EPI_ISL_19146802, EPI_ISL_19146858, EPI_ISL_19153455, EPI_ISL_19159145, EPI_ISL_19163087, EPI_ISL_19163147, EPI_ISL_19163196, EPI_ISL_19163258, EPI_ISL_19163279, EPI_ISL_19163290,

[xz-keg]

Designated KP.2.14 via cov-lineages/pango-designation@f08b13f

[xz-keg]

There seems to be many S:T22N branches under KP.2.14 in the newest usher tree. Do all seqs of KP.2.14 having S:T22N and those without T22N are just coverage issues, or is there many separate emergence of this?

@AngieHinrichs

[FedeGueli]

There seems to be many S:T22N branches under KP.2.14 in the newest usher tree. Do all seqs of KP.2.14 having S:T22N and those without T22N are just coverage issues, or is there many separate emergence of this?

@AngieHinrichs

Yeah noticed that too. KP.2.14 tough has not T22N as defining, but it is in most of the sequences belonging to this lineage.i think it is not ideal but dont see how to do better

[AngieHinrichs]

Yes, some sequences from Canada without S:T22N seem to be breaking up what could otherwise be one big S:T22N branch. I will add it to the list for the next round of prune & replace.

[FedeGueli]

the S:T22N designated KP.2.14.1 via cov-lineages/pango-designation@01948c2

[xz-keg]

KP.2.14.1 is retracted.