Events

Rhum 32: The Casino Game That Belongs to Trinidad and Tobago

Compellingly reinvent ubiquitous synergy vis-a-vis cost effective niche markets. Credibly leverage existing equity invested

Rhum 32: The Casino Game That Belongs to Trinidad and Tobago

One of the more important stories in Trinidad and Tobago’s gaming industry over the past year has come from the country’s online gaming agents, who have been publicly pressing for talks with the National Lotteries Control Board over what they say are serious operational and financial issues. For players, this matters because when agents complain about system problems, shutdowns and settlement structures, it can eventually affect convenience, access and trust in the gaming experience.

In July 2025, the Online Gaming Agents Association of Trinidad and Tobago called for an urgent meeting with the newly appointed NLCB board. According to Newsday, the association said it wanted to address a list of unresolved issues, including malfunctioning machines, machine suppression, over-the-counter deposit options, weekly settlement fees, reactivation fees and interest charges tied to alleged agent indebtedness.

A few days later, Guardian Media reported that the association’s president, Dean Persad, also accused the former board of unfairly penalising agents and arbitrarily shutting down gaming terminals. Guardian reported that Persad claimed these shutdowns were costing the State roughly TT$900,000 in revenue per week, while newly appointed NLCB chairman Ken Emrith said he expected to meet with stakeholders, including the association, in the coming weeks.

The issue did not disappear after that initial public appeal. By January 6, 2026, CNC3 reported that the association said it had made more than a dozen documented attempts to meet with the NLCB’s new board since July 25, 2025, without success. CNC3 also reported that the group claimed NLCB was losing more than TT$2 million per week because of what it described as imprudent management, and that a meeting scheduled for November 10 had been cancelled.

For local players, the technical complaints may sound like inside-baseball industry drama, but they are not irrelevant. If agents are dealing with broken terminals, disputed fees, account frictions or fewer payment options, players are the ones most likely to feel it through slower service, less convenience or reduced access at the retail level. That is an inference based on the issues the association publicly listed, not a confirmed statement from NLCB.

The broader reason this story matters is that Trinidad and Tobago’s gaming market still depends heavily on real-world agent and terminal networks. Unlike fully frictionless digital markets, local players often rely on physical points of contact, assisted deposits and in-person support. So when the agent network says it is under strain, that is not just an operator problem in the background. It has the potential to affect how smoothly the market works for everyday users. This is an inference drawn from the reported role of agents and the issues they raised.

At the same time, it is worth noting that these claims have largely come from the agents’ side of the dispute. Public reporting confirms the calls for meetings and outlines the complaints, but it does not establish that every allegation has been independently proven. What is clear, however, is that the disagreement has become public and persistent enough to signal deeper tension within the sector.

The takeaway for players is simple: this is a story worth watching. When agents push back this publicly, it usually means there are real commercial and operational pressures underneath. Whether those tensions lead to reform, better dialogue or a more fragmented gaming environment remains to be seen, but the outcome could have a direct effect on how local players interact with the market in 2026.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*

Lost Password