BIZTRAC BETA
Activities of advertising agencies

BRENNSTRØM CONSULT AS

Org. no. 928150550 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 51,000
Operating profit NOK 18,000
Equity NOK 68,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-23 Adresseendring registrert 2026-04-23.

BRENNSTRØM CONSULT AS is registered as a limited company in Oslo, Oslo with organisation number 928150550. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Konsulenttjenester”. The most recent filed accounts, for the 2025 financial year, show NOK 51,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 51,000
Operating profit
NOK 18,000
Equity
NOK 68,000
Est. value
NOK 102,000

Financial health · 2025

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

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

Who owns BRENNSTRØM CONSULT AS?

MATS SIMON BRENNSTRØM
BRENNSTRØM CONSULT AS
NOK 51,000 rev. · NOK 18,000 profit

BRENNSTRØM CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BRENNSTRØM CONSULT AS own?

BRENNSTRØM CONSULT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRENNSTRØM CONSULT AS

Who owns BRENNSTRØM CONSULT AS?

MATS SIMON BRENNSTRØM is the largest registered owner, with 100.0%.

What is the revenue of BRENNSTRØM CONSULT AS?

BRENNSTRØM CONSULT AS had revenue of NOK 51,000 in 2025.

Where is BRENNSTRØM CONSULT AS based?

BRENNSTRØM CONSULT AS has its business address in Oslo.

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.