Skip to content
Governance Register

The red node is Fazlul. Pale nodes are charities, grey nodes are companies, and darker grey nodes are the people who sit on them. Sign in free to explore further.

Person Preview

Fazlul Huq

Fazlul Huq is a holder of the role of secretary at Riomark Limited. Source: Companies House records.

Secretary at Riomark Limited

  • 1 current role
  • 1 previous role
  • Served alongside 115 people

Fazlul's network: 115 people across 2 organisations

Anyone can join - you don't need to be on the register. Used by researchers, journalists, recruiters and due diligence teams.

Private by default - we never tell anyone you looked them up. Viewing, searching, saving and shortlisting are private; people only hear from you if you choose to send them a message.

Official record Companies House · updated 11th October 2026 · Free, no card or password

Current roles

2 roles across 2 organisations
  • Riomark Limited
    Secretary · Current
    Official record ยท Companies House
    Source
    Companies House
    Organisation
    Riomark Limited
    Role
    Secretary
    Record reference
    Company 01394483
    Current

1 more role, including 1 previous role, with dates and sources

Sign in free to see all roles

People Fazlul has served alongside

115 people across 2 organisations

Based on overlapping official board records. Calculated from official records

115 people across 2 organisations

Create a free account to reveal this governance network and see how you're connected.

Create a free account to reveal

Connections

Connection map

The organisations and people around Fazlul, shown in full after you sign in.

How are you connected?

Create a free account to see the recorded route between you and Fazlul, if there is one.

Create a free account to check

Sources

Companies House
Officer appointments and resignations.
Edition
Register edition compiled 11th October 2026
Identity
Records are treated as the same person only where the evidence confirms it. How people are matched

Report an issue with this record · How we handle data