BIZTRAC BETA
Motion picture, video and television programme production activities

ABOVE MEDIA AS

Org. no. 923213279 Limited company (AS) Bærum Incorporated 1934 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK 40,000
Equity NOK 429,000
Incorporated 1934
Share capital NOK 30,000

ABOVE MEDIA AS is registered as a limited company in Bærum, Akershus with organisation number 923213279. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 1934. Registered share capital is NOK 30,000, divided into 1440 shares. The company's stated purpose is: “Dronetjenester innenfor tv-, reklame-, film-, media- og event-bransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK 40,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK 40,000
Equity
NOK 429,000
Est. value
NOK 436,000

Financial health · 2024

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

Who owns ABOVE MEDIA AS?

MATIAS BRAATHEN
ABOVE MEDIA AS
NOK 4.1m rev. · NOK 40,000 profit

ABOVE MEDIA AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ABOVE MEDIA AS own?

ABOVE MEDIA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ABOVE MEDIA AS

Who owns ABOVE MEDIA AS?

MATIAS BRAATHEN is the largest registered owner, with 55.0%.

What is the revenue of ABOVE MEDIA AS?

ABOVE MEDIA AS had revenue of NOK 4.1m in 2024.

Who is the general manager of ABOVE MEDIA AS?

William Ekevall Schaad is registered as general manager of ABOVE MEDIA AS.

Where is ABOVE MEDIA AS based?

ABOVE MEDIA AS has its business address in Eiksmarka.

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.