BIZTRAC BETA
Other construction installation

TRØNDELAG PORTSERVICE AS

Org. no. 986139176 Limited company (AS) Trondheim Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK 1.7m
Equity NOK 1.8m
Incorporated 2003
Share capital NOK 118,000

TRØNDELAG PORTSERVICE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 986139176. The business is classified under other construction installation (NACE 43.240). The company was incorporated in 2003. Registered share capital is NOK 118,000, divided into 118 shares. The company's stated purpose is: “Salg, levering og montering av garasje- og industriporter, dokkingsystem, produksjon og montering av rullegitter, samt alt hva hermed hører med.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.2m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK 1.7m
Equity
NOK 1.8m
Est. value
NOK 6.0m

Financial health · 2024

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

Who owns TRØNDELAG PORTSERVICE AS?

ORYX HOLDING AS
TRØNDELAG PORTSERVICE AS
NOK 8.2m rev. · NOK 1.7m profit

TRØNDELAG PORTSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRØNDELAG PORTSERVICE AS

Who owns TRØNDELAG PORTSERVICE AS?

ORYX HOLDING AS is the largest registered owner, with 84.7%.

What is the revenue of TRØNDELAG PORTSERVICE AS?

TRØNDELAG PORTSERVICE AS had revenue of NOK 8.2m in 2024.

Who is the general manager of TRØNDELAG PORTSERVICE AS?

Arild Steinar Kraft is registered as general manager of TRØNDELAG PORTSERVICE AS.

Where is TRØNDELAG PORTSERVICE AS based?

TRØNDELAG PORTSERVICE AS has its business address in Ranheim.

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.