BIZTRAC BETA
Activities of advertising agencies

W3 MEDIA AS

Org. no. 913010655 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 72,000
Operating profit NOK 51,000
Equity NOK 71,000
Incorporated 2013
Share capital NOK 30,000

W3 MEDIA AS is registered as a limited company in Bergen, Vestland with organisation number 913010655. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av konsulenttjenester innen markedsføring og salg på internett/mobil samt utvikling av internettløsninger. I tillegg har selskapet som formål å drive salg av tjenester og andre produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 72,000 in revenue and NOK 51,000 in operating profit.

Key figures · 2024

Revenue
NOK 72,000
Operating profit
NOK 51,000
Equity
NOK 71,000
Est. value
NOK 210,000

Financial health · 2024

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

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

Who owns W3 MEDIA AS?

MAGNUS FJELLAND LUDVIGSEN
W3 MEDIA AS
NOK 72,000 rev. · NOK 51,000 profit

W3 MEDIA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about W3 MEDIA AS

Who owns W3 MEDIA AS?

MAGNUS FJELLAND LUDVIGSEN is the largest registered owner, with 50.0%.

What is the revenue of W3 MEDIA AS?

W3 MEDIA AS had revenue of NOK 72,000 in 2024.

Who is the general manager of W3 MEDIA AS?

Magnus Fjelland Ludvigsen is registered as general manager of W3 MEDIA AS.

Where is W3 MEDIA AS based?

W3 MEDIA AS has its business address in Bergen.

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.