Skip to content
Governance Register

The red node is Lukas. 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

Lukas Gregor Konstantin Lehmann

Lukas Gregor Konstantin Lehmann has 1 previous role on record and no current roles. Source: Companies House records.

Director at Firsthand Lothian

  • 0 current roles
  • 1 previous role
  • Served alongside 23 people

Lukas's network: 23 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 4th October 2026 · Free, no card or password

Roles

1 role across 1 organisation
  • Firsthand Lothian
    Director · 2007-2009
    Official record ยท Companies House
    Source
    Companies House
    Organisation
    Firsthand Lothian
    Role
    Director
    Appointed
    2007-12-06
    Ended
    2009-03-31
    Record reference
    Company SC140769
    Previous

People Lukas has served alongside

23 people across 2 organisations

Based on overlapping official board records. Calculated from official records

23 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 Lukas, shown in full after you sign in.

How are you connected?

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

Create a free account to check

Sources

Companies House
Officer appointments and resignations.
Edition
Register edition compiled 4th 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