biztrac. BETA
COMPANY REGISTER PROFILE
929528158 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other education activities

LAURENTIUS CONSULT AS

Org. no. 929528158 Limited company (AS) Lillestrøm Incorporated 2022 Active
Revenue 2025 NOK 23,000
Operating profit NOK −36,000
Equity NOK −38,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−38k kr).

LAURENTIUS CONSULT AS is registered as a limited company in Lillestrøm, Akershus with organisation number 929528158. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester innen dokumentasjonsforvalting og arkiv. Enkle catering og opplæringsoppdrag.”. The most recent filed accounts, for the 2025 financial year, show NOK 23,000 in revenue and NOK −36,000 in operating profit.

Key figures · 2025

Revenue
NOK 23,000
▼ −83 %
Operating profit
NOK −36,000
▼ −86 %
Equity
NOK −38,000
▼ −139 %

Financial health · 2025

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

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

Who owns LAURENTIUS CONSULT AS?

LAURENTIUS CONSULT AS
NOK 23,000 rev. · NOK −36,000 profit

LAURENTIUS CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAURENTIUS CONSULT AS

Who owns LAURENTIUS CONSULT AS?

Geir Magnus Walderhaug is the largest registered owner, with 100.0%.

What is the revenue of LAURENTIUS CONSULT AS?

LAURENTIUS CONSULT AS had revenue of NOK 23,000 in 2025.

Where is LAURENTIUS CONSULT AS based?

LAURENTIUS CONSULT AS has its business address in Lillestrøm.

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

Report a problem

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