biztrac. BETA
COMPANY REGISTER PROFILE
929607597 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of advertising agencies

BRANDHUB AS

Org. no. 929607597 Limited company (AS) Bærum Incorporated 2022 Active
Revenue 2025 NOK 30,000
Operating profit NOK 25,000
Equity NOK 753,000
Incorporated 2022
Share capital NOK 90,000

BRANDHUB AS is registered as a limited company in Bærum, Akershus with organisation number 929607597. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2022. Registered share capital is NOK 90,000, divided into 90 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor marketing bransjen og andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 30,000 in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 30,000
▼ −86 %
Operating profit
NOK 25,000
▼ −87 %
Equity
NOK 753,000
▲ +3 %
Est. value
NOK 695,000

Financial health · 2025

Liquidity
11.12
Very good
Current assets ÷ current liabilities
Profitability
3.3%
Weak
Return on total assets
Solidity
99.3%
Very good
Equity as a share of total capital

Who owns BRANDHUB AS?

BRANDHUB AS
NOK 30,000 rev. · NOK 25,000 profit

BRANDHUB AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRANDHUB AS own?

BRANDHUB AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRANDHUB AS

Who owns BRANDHUB AS?

SVEST1 INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of BRANDHUB AS?

BRANDHUB AS had revenue of NOK 30,000 in 2025.

Who is the general manager of BRANDHUB AS?

Simon Helge Aavatsmark Vestvik is registered as general manager of BRANDHUB AS.

Where is BRANDHUB AS based?

BRANDHUB AS has its business address in Jar.

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

Report a problem

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