biztrac. BETA
COMPANY REGISTER PROFILE
924532661 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

MOERVEIEN WOOD AS

Org. no. 924532661 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 44,000
Equity NOK 23.3m
Incorporated 2020
Share capital NOK 26.0m

MOERVEIEN WOOD AS is registered as a limited company in Bærum, Akershus with organisation number 924532661. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 26.0m, divided into 26030 shares. The company's stated purpose is: “Utleie, utvikling, utbygging og salg av fast eiendom og det som står i forbindelse med dette. Selskapet kan i den forbindelse stille garantier og andre sikkerheter ved låneopptak og andre disposisjoner knyttet til virksomheten.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 44,000 in operating profit.

Former names: STTI HOLDING AS

Key figures · 2025

Revenue
NOK 2.0m
▼ −14 %
Operating profit
NOK 44,000
▲ +111 %
Equity
NOK 23.3m
▼ −1 %
Est. value
NOK 16.2m

Financial health · 2025

Liquidity
3.53
Very good
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
22.9%
Good
Equity as a share of total capital

Who owns MOERVEIEN WOOD AS?

MOERVEIEN WOOD AS
NOK 2.0m rev. · NOK 44,000 profit

MOERVEIEN WOOD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOERVEIEN WOOD AS

Who owns MOERVEIEN WOOD AS?

NORDR NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of MOERVEIEN WOOD AS?

MOERVEIEN WOOD AS had revenue of NOK 2.0m in 2025.

Where is MOERVEIEN WOOD AS based?

MOERVEIEN WOOD AS has its business address in Fornebu.

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.