BIZTRAC BETA
Public relations and communication activities

KONGELF MEDIA AS

Org. no. 917293546 Limited company (AS) Nordre Follo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 475,000
Operating profit NOK −142,000
Equity NOK 143,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

KONGELF MEDIA AS is registered as a limited company in Nordre Follo, Akershus with organisation number 917293546. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive konsulentvirksomhet innen PR og kommunikasjon og ellers alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 475,000 in revenue and NOK −142,000 in operating profit.

Key figures · 2025

Revenue
NOK 475,000
Operating profit
NOK −142,000
Equity
NOK 143,000
Est. value
NOK 568,000

Financial health · 2025

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

Who owns KONGELF MEDIA AS?

STEFFEN KONGELF
KONGELF MEDIA AS
NOK 475,000 rev. · NOK −142,000 profit

KONGELF MEDIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGELF MEDIA AS

Who owns KONGELF MEDIA AS?

STEFFEN KONGELF is the largest registered owner, with 100.0%.

What is the revenue of KONGELF MEDIA AS?

KONGELF MEDIA AS had revenue of NOK 475,000 in 2025.

Who is the general manager of KONGELF MEDIA AS?

Steffen Kongelf is registered as general manager of KONGELF MEDIA AS.

Where is KONGELF MEDIA AS based?

KONGELF MEDIA AS has its business address in Trollåsen.

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.