BIZTRAC BETA
Other specialised construction activities n.e.c.

BMS NORGE AS

Org. no. 995992523 Limited company (AS) Drammen Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −390,000
Incorporated 2010
Share capital NOK 100,000

Signals

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

BMS NORGE AS is registered as a limited company in Drammen, Buskerud with organisation number 995992523. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er utleie av arbeidskraft og entreprenørvirksomhet. Selskapet kan også engasjere seg i import og eksport av varer, samt kjøp og salg av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −390,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns BMS NORGE AS?

BJØRN EGIL GUNNERUD
BMS NORGE AS
NOK 0 rev. · NOK 0 profit

BMS NORGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BMS NORGE AS

Who owns BMS NORGE AS?

BJØRN EGIL GUNNERUD is the largest registered owner, with 50.0%.

What is the revenue of BMS NORGE AS?

BMS NORGE AS had revenue of NOK 0 in 2025.

Who is the general manager of BMS NORGE AS?

Bjørn Egil Gunnerud is registered as general manager of BMS NORGE AS.

Where is BMS NORGE AS based?

BMS NORGE AS has its business address in Drammen.

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.