biztrac. BETA
COMPANY REGISTER PROFILE
925089311 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of household, office and shop furniture, carpets and lighting equipment

ALNABRU INVEST AS

Org. no. 925089311 Limited company (AS) Vestby Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −75,000
Equity NOK 29.5m
Incorporated 2020
Share capital NOK 8.5m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−75k kr).

ALNABRU INVEST AS is registered as a limited company in Vestby, Akershus with organisation number 925089311. The business is classified under wholesale of household, office and shop furniture, carpets and lighting equipment (NACE 46.470). The company was incorporated in 2020. Registered share capital is NOK 8.5m, divided into 8500000 shares. The company's stated purpose is: “Drive handel og engrosvirksomhet med møbler og tilknyttede produkter gjennom å eie aksjer i selskaper som i det vesentlige driver slik virksomhet, samt virksomhet beslektet med eller tilknyttet dette.”.

Key figures · 2025

Operating profit
NOK −75,000
▼ −68 %
Equity
NOK 29.5m
▼ −34 %
Est. value
NOK 21.3m

Financial health · 2025

Liquidity
0.72
Weak
Current assets ÷ current liabilities
Profitability
-10.8%
Not satisfactory
Return on total assets
Solidity
29.2%
Good
Equity as a share of total capital

Who owns ALNABRU INVEST AS?

ALNABRU INVEST AS
· NOK −75,000 profit

ALNABRU INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ALNABRU INVEST AS own?

ALNABRU INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ALNABRU INVEST AS

Who owns ALNABRU INVEST AS?

BIRKELUNDEN INVESTERINGSSELSKAP AS is the largest registered owner, with 100.0%.

Where is ALNABRU INVEST AS based?

ALNABRU INVEST AS has its business address in Vestby.

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.