BIZTRAC BETA
Activities of advertising agencies

VISJON MEDIA AS

Org. no. 930747858 Limited company (AS) Osterøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 32,000
Operating profit NOK −10,000
Equity NOK 29,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).
  • Nylig endring 2026-02-03 Adresseendring registrert 2026-02-03.

VISJON MEDIA AS is registered as a limited company in Osterøy, Vestland with organisation number 930747858. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Markedsføringsinnhold/medieproduksjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 32,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 32,000
Operating profit
NOK −10,000
Equity
NOK 29,000
Est. value
NOK 48,000

Financial health · 2025

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

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

Who owns VISJON MEDIA AS?

DANIEL BJØRNEBEKK
VISJON MEDIA AS
NOK 32,000 rev. · NOK −10,000 profit

VISJON MEDIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VISJON MEDIA AS

Who owns VISJON MEDIA AS?

DANIEL BJØRNEBEKK is the largest registered owner, with 100.0%.

What is the revenue of VISJON MEDIA AS?

VISJON MEDIA AS had revenue of NOK 32,000 in 2025.

Who is the general manager of VISJON MEDIA AS?

Daniel Bjørnebekk is registered as general manager of VISJON MEDIA AS.

Where is VISJON MEDIA AS based?

VISJON MEDIA AS has its business address in Lonevåg.

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.