BIZTRAC BETA
COMPANY REGISTER PROFILE
916292457 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Legal activities

ADVOKAT BAKLUND CBA

Org. no. 916292457 Sole proprietorship (ENK) Oslo Active
Ownership graph ↗
Revenue 2025 NOK 445,000
Operating profit NOK 49,000
Equity NOK 165,000

ADVOKAT BAKLUND CBA is registered as a sole proprietorship in Oslo, Oslo with organisation number 916292457. The business is classified under legal activities (NACE 69.100). The most recent filed accounts, for the 2025 financial year, show NOK 445,000 in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 445,000
Operating profit
NOK 49,000
Equity
NOK 165,000
Est. value
NOK 354,000

Financial health · 2025

Liquidity
4.16
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
80.0%
Very good
Equity as a share of total capital

Who owns ADVOKAT BAKLUND CBA?

No shareholders are registered for ADVOKAT BAKLUND CBA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ADVOKAT BAKLUND CBA

What is the revenue of ADVOKAT BAKLUND CBA?

ADVOKAT BAKLUND CBA had revenue of NOK 445,000 in 2025.

Who is the general manager of ADVOKAT BAKLUND CBA?

Christian Baklund is registered as general manager of ADVOKAT BAKLUND CBA.

Where is ADVOKAT BAKLUND CBA based?

ADVOKAT BAKLUND CBA has its business address in Oslo.

Property

Business address Blåskjellveien 3, 0139 Oslo
Cadastral unit 301-195/51/0/0
Building Tomannsbolig, horisontaldelt · 4 units

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.