jL reveals contract disagreements blocked move to MOUZ

Photo: Michal Konkol / pley.gg

jL reveals contract disagreements blocked move to MOUZ

The Lithuanian CS2 star says he wanted to stay with MOUZ permanently but will now ride out a short-term Vitality stint before hunting for a new home.

Justinas “jL” Lekavicius wanted to make things work with MOUZ. The feeling, apparently, was mutual. But professional Counter-Strike, like most esports, runs on contracts, and contracts have a way of ruining perfectly good plans.

The Lithuanian rifler revealed that disagreements over contract terms prevented what would have been a permanent move to the German organization following his loan spell in April and May 2026. Instead of settling into a long-term role, jL found himself back on the open market, eventually landing as a temporary stand-in for Team Vitality.

Advertisement

A loan that worked on the server, not on paper

jL’s time with MOUZ was, by competitive standards, a success. During his two-month loan, the team secured third-place finishes at both PGL Astana and the CS Asian Championships. For a roster in transition, that kind of consistency from a borrowed player is exactly the sort of thing that makes organizations want to make the relationship permanent.

MOUZ has since moved on, promoting academy player xelex to the main roster as part of a broader overhaul.

From NaVi to free agency to filling in

jL departed Natus Vincere in July 2026, ending what had been a high-profile stint with one of Counter-Strike’s most storied organizations, which had included a title-winning run at IEM Rio 2024.

Both mezii and apEX are currently on paternity leave at Team Vitality, creating roster gaps that needed filling. jL stepped in as a stand-in, covering several upcoming events, including BLAST Open Porto and PGL Masters Bucharest.

jL has made his intentions clear: once the Vitality stint wraps up, he plans to pursue a full-time roster spot elsewhere.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.
jL reveals contract disagreements blocked move to MOUZ
jL reveals contract disagreements blocked move to MOUZ

The Lithuanian CS2 star says he wanted to stay with MOUZ permanently but will now ride out a short-term Vitality stint before hunting for a new home.

Photo: Michal Konkol / pley.gg

Justinas “jL” Lekavicius wanted to make things work with MOUZ. The feeling, apparently, was mutual. But professional Counter-Strike, like most esports, runs on contracts, and contracts have a way of ruining perfectly good plans.

The Lithuanian rifler revealed that disagreements over contract terms prevented what would have been a permanent move to the German organization following his loan spell in April and May 2026. Instead of settling into a long-term role, jL found himself back on the open market, eventually landing as a temporary stand-in for Team Vitality.

Advertisement

A loan that worked on the server, not on paper

jL’s time with MOUZ was, by competitive standards, a success. During his two-month loan, the team secured third-place finishes at both PGL Astana and the CS Asian Championships. For a roster in transition, that kind of consistency from a borrowed player is exactly the sort of thing that makes organizations want to make the relationship permanent.

MOUZ has since moved on, promoting academy player xelex to the main roster as part of a broader overhaul.

From NaVi to free agency to filling in

jL departed Natus Vincere in July 2026, ending what had been a high-profile stint with one of Counter-Strike’s most storied organizations, which had included a title-winning run at IEM Rio 2024.

Both mezii and apEX are currently on paternity leave at Team Vitality, creating roster gaps that needed filling. jL stepped in as a stand-in, covering several upcoming events, including BLAST Open Porto and PGL Masters Bucharest.

jL has made his intentions clear: once the Vitality stint wraps up, he plans to pursue a full-time roster spot elsewhere.

Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.