BIZTRAC BETA
Other captive investment companies

STYRBORD AS

Org. no. 888870822 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 8.9m
Operating profit NOK 7.3m
Equity NOK 156.2m
Incorporated 2005
Share capital NOK 300,000

STYRBORD AS is registered as a limited company in Oslo, Oslo with organisation number 888870822. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå investering i aksjer, obligasjoner, selskapsandeler og andre verdipapirer, samt erverv, utvikling, forvaltning og omsetning av faste eiendommer samt utlån tilknyttet investeringer og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.9m in revenue and NOK 7.3m in operating profit.

Key figures · 2024

Revenue
NOK 8.9m
Operating profit
NOK 7.3m
Equity
NOK 156.2m
Est. value
NOK 107.3m

Financial health · 2024

Liquidity
15.86
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
94.6%
Very good
Equity as a share of total capital

Who owns STYRBORD AS?

JAN TELLEF THORLEIFSSON
STYRBORD AS
NOK 8.9m rev. · NOK 7.3m profit

STYRBORD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STYRBORD AS own?

STYRBORD AS holds stakes in 12 companies:

See the full ownership structure →

Frequently asked questions about STYRBORD AS

Who owns STYRBORD AS?

JAN TELLEF THORLEIFSSON is the largest registered owner, with 100.0%.

What is the revenue of STYRBORD AS?

STYRBORD AS had revenue of NOK 8.9m in 2024.

Where is STYRBORD AS based?

STYRBORD AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.