biztrac. BETA
COMPANY REGISTER PROFILE
919438312 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

BEI HOLDING AS

Org. no. 919438312 Limited company (AS) Rælingen Incorporated 2017 Active
Revenue 2025 NOK 16,000
Operating profit NOK −67,000
Equity NOK 518,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

BEI HOLDING AS is registered as a limited company in Rælingen, Akershus with organisation number 919438312. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer i andre selskaper og alt hva hermed står i forbindelse. Selskapet kan eie fast eiendom, påta seg konsulentoppdrag og drive med maskin og redskapsutleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK −67,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
▲ +31 %
Operating profit
NOK −67,000
▲ +6 %
Equity
NOK 518,000
▼ −11 %
Est. value
NOK 269,000

Financial health · 2025

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
-9.2%
Not satisfactory
Return on total assets
Solidity
73.4%
Very good
Equity as a share of total capital

Who owns BEI HOLDING AS?

BEI HOLDING AS
NOK 16,000 rev. · NOK −67,000 profit

BEI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEI HOLDING AS

Who owns BEI HOLDING AS?

Børge Einar Iversen is the largest registered owner, with 100.0%.

What is the revenue of BEI HOLDING AS?

BEI HOLDING AS had revenue of NOK 16,000 in 2025.

Where is BEI HOLDING AS based?

BEI HOLDING AS has its business address in Rælingen.

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.