BIZTRAC BETA
COMPANY REGISTER PROFILE
924749466 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other content distribution activities

B2LA AS

Org. no. 924749466 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK −283,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−283k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

B2LA AS is registered as a limited company in Asker, Akershus with organisation number 924749466. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Informasjonstjenester.”.

Key figures · 2025

Operating profit
NOK −22,000
▲ +34 %
Equity
NOK −283,000
▼ −10 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
-20474.9%
Not satisfactory
Return on total assets
Solidity
-416248.5%
Weak
Equity as a share of total capital

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

Who owns B2LA AS?

B2LA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about B2LA AS

Who owns B2LA AS?

EDCA05 AS is the largest registered owner, with 95.0%.

Where is B2LA AS based?

B2LA AS has its business address in Sætre.

Property

Business address Storsandveien 26, 3475 Sætre
Cadastral unit 3203-353/97/0/0
Building Enebolig · 1 unit

2 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.