BIZTRAC BETA
COMPANY REGISTER PROFILE
931300113 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LAUMA AS

Org. no. 931300113 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 9,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).
  • Nylig endring 2026-07-13 Adresseendring registrert 2026-07-13.

LAUMA AS is registered as a limited company in Bærum, Akershus with organisation number 931300113. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 9,000
Est. value
NOK 10,000

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 LAUMA AS?

KRISTIAN HJELSET
LAUMA AS
NOK 0 rev. · NOK −8,000 profit

LAUMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAUMA AS

Who owns LAUMA AS?

KRISTIAN HJELSET is the largest registered owner, with 100.0%.

What is the revenue of LAUMA AS?

LAUMA AS had revenue of NOK 0 in 2025.

Where is LAUMA AS based?

LAUMA AS has its business address in Blommenholm.

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.