BIZTRAC BETA
Business and other management consultancy activities

BRANDSTORY AS

Org. no. 935839963 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 655,000
Operating profit NOK 85,000
Equity NOK 90,000
Incorporated 2025
Share capital NOK 30,000

BRANDSTORY AS is registered as a limited company in Oslo, Oslo with organisation number 935839963. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Strategi- og merkevarerådgiving, tekstarbeid og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 655,000 in revenue and NOK 85,000 in operating profit.

Key figures · 2025

Revenue
NOK 655,000
Operating profit
NOK 85,000
Equity
NOK 90,000
Est. value
NOK 471,000

Financial health · 2025

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.5%
Weak
Equity as a share of total capital

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

Who owns BRANDSTORY AS?

FENRIS HOLDING AS
BRANDSTORY AS
NOK 655,000 rev. · NOK 85,000 profit

BRANDSTORY AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BRANDSTORY AS er morselskap for 1 datterselskap:

Frequently asked questions about BRANDSTORY AS

Who owns BRANDSTORY AS?

FENRIS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BRANDSTORY AS?

BRANDSTORY AS had revenue of NOK 655,000 in 2025.

Where is BRANDSTORY AS based?

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