BIZTRAC BETA
Publishing of newspapers

MEDIEHUSET INNHERRED AS

Org. no. 915106641 Limited company (AS) Verdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 37.1m
Operating profit NOK 737,000
Equity NOK 11.1m
Incorporated 2015
Employees 21
Share capital NOK 3.0m

MEDIEHUSET INNHERRED AS is registered as a limited company in Verdal, Trøndelag with organisation number 915106641. The business is classified under publishing of newspapers (NACE 58.120). The company was incorporated in 2015 and has 21 registered employees. Registered share capital is NOK 3.0m, divided into 3000 shares. The company's stated purpose is: “Produksjon og utgivelse av lokalavis på papir og nett i Levanger og Verdal samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 37.1m in revenue and NOK 737,000 in operating profit.

Key figures · 2024

Revenue
NOK 37.1m
Operating profit
NOK 737,000
Equity
NOK 11.1m
Est. value
NOK 8.5m

Financial health · 2024

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

Who owns MEDIEHUSET INNHERRED AS?

LEVANGER-AVISA AS
MEDIEHUSET INNHERRED AS
NOK 37.1m rev. · NOK 737,000 profit

MEDIEHUSET INNHERRED AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MEDIEHUSET INNHERRED AS

Who owns MEDIEHUSET INNHERRED AS?

LEVANGER-AVISA AS is the largest registered owner, with 50.0%.

What is the revenue of MEDIEHUSET INNHERRED AS?

MEDIEHUSET INNHERRED AS had revenue of NOK 37.1m in 2024.

Who is the general manager of MEDIEHUSET INNHERRED AS?

Odd Arild Sandnes is registered as general manager of MEDIEHUSET INNHERRED AS.

Where is MEDIEHUSET INNHERRED AS based?

MEDIEHUSET INNHERRED AS has its business address in Verdal.

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.