BIZTRAC BETA
Public relations and communication activities

&DALE AS

Org. no. 932685256 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 43,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

&DALE AS is registered as a limited company in Oslo, Oslo with organisation number 932685256. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapet skal selge varer og tjenester innen PR og kommunikasjonsarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 43,000
Est. value
NOK 81,000

Financial health · 2025

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

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

Who owns &DALE AS?

HENRIK MARIERO DALE
&DALE AS
NOK 0 rev. · NOK −6,000 profit

&DALE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does &DALE AS own?

&DALE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about &DALE AS

Who owns &DALE AS?

HENRIK MARIERO DALE is the largest registered owner, with 100.0%.

What is the revenue of &DALE AS?

&DALE AS had revenue of NOK 0 in 2025.

Where is &DALE AS based?

&DALE 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.