Ugonna Go or No?

Kentucky basketball fans have been left wondering: will Ugonna Kingsley Onyenso stay or go? The 6’10” sophomore recently announced that he’s entering the transfer portal, but there are rumors that he may still have a shot at returning to the Wildcats.

It’s no secret that Ugonna’s time at Kentucky has been a bit of rollercoaster ride, despite fans believing he was playing his part. He struggled to get minutes during his freshman year, but showed flashes of potential when he did get on the court. This year, he came into the season with high hopes and looked poised to be a key contributor for the Wildcats.

Ugonna played in just 14 games, averaging 2.4 points and 2.3 rebounds in 9.3 minutes per game. He never seemed to get the minutes his “camp” wanted and suddenly rumors started to swirl about his future at Kentucky.

Just a few days ago, Ugonna announced that he was entering the transfer portal. It came as a surprise to many, but some fans couldn’t help but wonder if it was the right decision. After all, Ugonna was still under scholarship at Kentucky and had a chance to not only fight for playing time, but perhaps be a star for the next season.

Rumors have since emerged that there’s a door open for Ugonna to return to Kentucky. Some fans are hopeful that he’ll take advantage of the opportunity and stay in Lexington. Others, however, feel that it’s time for him to move on and find a better fit elsewhere.

So, what’s the verdict? Should Ugonna go or no? It’s a tough call, but ultimately it’s up to him and his camp. If he feels that he’ll be able to thrive in a new environment, then it’s probably best for him to move on. On the other hand, if he believes that he can make a significant contribution to the Wildcats next season, then he should seriously consider returning.

One thing’s for sure: Kentucky fans will be eagerly waiting to see what Ugonna decides. Whatever he chooses, we wish him the best of luck in his future endeavors.

What do you think, should Ugonna go or no?

Update: great article by @jackpilgrim covering this topic with additional details. Click to read.