BIZTRAC BETA
Publishing of newspapers

ENEBAKK AVIS AS

Org. no. 981518632 Limited company (AS) Enebakk Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK 475,000
Equity NOK 7.2m
Incorporated 1999
Employees 6
Share capital NOK 500,000

ENEBAKK AVIS AS is registered as a limited company in Enebakk, Akershus with organisation number 981518632. The business is classified under publishing of newspapers (NACE 58.120). The company was incorporated in 1999 and has 6 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Avisdrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK 475,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK 475,000
Equity
NOK 7.2m
Est. value
NOK 7.1m

Financial health · 2024

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

Who owns ENEBAKK AVIS AS?

SMAALENENE MEDIER AS
ENEBAKK AVIS AS
NOK 7.2m rev. · NOK 475,000 profit

ENEBAKK AVIS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ENEBAKK AVIS AS own?

ENEBAKK AVIS AS holds a stake in 1 company:

See the full ownership structure →

Group structure

ENEBAKK AVIS AS er morselskap for 74 datterselskaper:

Frequently asked questions about ENEBAKK AVIS AS

Who owns ENEBAKK AVIS AS?

SMAALENENE MEDIER AS is the largest registered owner, with 100.0%.

What is the revenue of ENEBAKK AVIS AS?

ENEBAKK AVIS AS had revenue of NOK 7.2m in 2024.

Who is the general manager of ENEBAKK AVIS AS?

Gunnleik Seierstad is registered as general manager of ENEBAKK AVIS AS.

Where is ENEBAKK AVIS AS based?

ENEBAKK AVIS AS has its business address in Enebakk.

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.