BIZTRAC BETA
Rental and operating of own or leased real estate

LABYRINT AS

Org. no. 988524433 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 317,000
Operating profit NOK 168,000
Equity NOK 73,000
Incorporated 2005
Share capital NOK 100,000

LABYRINT AS is registered as a limited company in Bærum, Akershus with organisation number 988524433. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investere i eiendom og aksjer og hermed forbundet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 317,000 in revenue and NOK 168,000 in operating profit.

Key figures · 2024

Revenue
NOK 317,000
Operating profit
NOK 168,000
Equity
NOK 73,000
Est. value
NOK 337,000

Financial health · 2024

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LABYRINT AS?

EVA MARIE-ANNE ZAKRISSON
LABYRINT AS
NOK 317,000 rev. · NOK 168,000 profit

LABYRINT AS has 4 registered shareholders:

All shareholders and roles →

Which companies does LABYRINT AS own?

LABYRINT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LABYRINT AS

Who owns LABYRINT AS?

EVA MARIE-ANNE ZAKRISSON is the largest registered owner, with 48.0%.

What is the revenue of LABYRINT AS?

LABYRINT AS had revenue of NOK 317,000 in 2024.

Who is the general manager of LABYRINT AS?

Hein Espen Hattestad is registered as general manager of LABYRINT AS.

Where is LABYRINT AS based?

LABYRINT AS has its business address in Stabekk.

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.