BIZTRAC BETA
Publishing of newspapers

TROLLHEIMSPORTEN AS

Org. no. 990696721 Limited company (AS) Rindal Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 23,000
Equity NOK 623,000
Incorporated 2006
Employees 20
Share capital NOK 688,000

TROLLHEIMSPORTEN AS is registered as a limited company in Rindal, Trøndelag with organisation number 990696721. The business is classified under publishing of newspapers (NACE 58.120). The company was incorporated in 2006 and has 20 registered employees. Registered share capital is NOK 688,000, divided into 43 shares. The company's stated purpose is: “Videreutvikle og drifte nettportalen www.trollheimsporten.no, og derigjennom søke å dekke distriktets behov for informasjon og kommunikasjon ut fra nærings- og samfunnsmessige behov.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 23,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 23,000
Equity
NOK 623,000
Est. value
NOK 500,000

Financial health · 2025

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

Who owns TROLLHEIMSPORTEN AS?

RINDAL NÆRINGSFORUM
TROLLHEIMSPORTEN AS
NOK 2.1m rev. · NOK 23,000 profit

TROLLHEIMSPORTEN AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about TROLLHEIMSPORTEN AS

Who owns TROLLHEIMSPORTEN AS?

RINDAL NÆRINGSFORUM is the largest registered owner, with 53.5%.

What is the revenue of TROLLHEIMSPORTEN AS?

TROLLHEIMSPORTEN AS had revenue of NOK 2.1m in 2024.

Who is the general manager of TROLLHEIMSPORTEN AS?

Bård Inge Romundstad is registered as general manager of TROLLHEIMSPORTEN AS.

Where is TROLLHEIMSPORTEN AS based?

TROLLHEIMSPORTEN AS has its business address in Rindal.

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.