BIZTRAC BETA
COMPANY REGISTER PROFILE
916621000 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

B SAFE AS

Org. no. 916621000 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 182,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

B SAFE AS is registered as a limited company in Bærum, Akershus with organisation number 916621000. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Forvalte eierskap i andre selskaper, herunder kapitalinteresser som hører inn under dette.”.

Key figures · 2024

Operating profit
NOK −1,000
Equity
NOK 182,000
Est. value
NOK 213,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.8%
Good
Equity as a share of total capital

Who owns B SAFE AS?

B SAFE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does B SAFE AS own?

B SAFE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about B SAFE AS

Who owns B SAFE AS?

OLE MARTIN BERG is the largest registered owner, with 50.0%.

Where is B SAFE AS based?

B SAFE AS has its business address in Bærums Verk.

Property

Business address Helsetdammen 20, 1353 Bærums Verk
Cadastral unit 3201-118/412/0/0
Building Enebolig · 1 unit

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.