BIZTRAC BETA
Other content distribution activities

OWESEN VENTURE AS

Org. no. 925099864 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 396,000
Equity NOK 1.5m
Incorporated 2020
Share capital NOK 41,000

OWESEN VENTURE AS is registered as a limited company in Oslo, Oslo with organisation number 925099864. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2020. Registered share capital is NOK 41,000, divided into 408 shares. The company's stated purpose is: “Drive investerings- og holdingsvirksomhet, herunder eie aksjer, andeler og andre finansielle instrumenter, samt annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 396,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 396,000
Equity
NOK 1.5m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns OWESEN VENTURE AS?

MARIUS OWESEN
OWESEN VENTURE AS
NOK 1.1m rev. · NOK 396,000 profit

OWESEN VENTURE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OWESEN VENTURE AS own?

OWESEN VENTURE AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

OWESEN VENTURE AS er morselskap for 2 datterselskaper:

Frequently asked questions about OWESEN VENTURE AS

Who owns OWESEN VENTURE AS?

MARIUS OWESEN is the largest registered owner, with 100.0%.

What is the revenue of OWESEN VENTURE AS?

OWESEN VENTURE AS had revenue of NOK 1.1m in 2025.

Where is OWESEN VENTURE AS based?

OWESEN VENTURE 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.