BIZTRAC BETA
Repair and maintenance of civilian ships and boats

EIDKJOSEN INDUSTRIPARK AS

Org. no. 954132080 Limited company (AS) Tromsø Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 438,000
Equity NOK 5.2m
Incorporated 1989
Share capital NOK 536,000

Signals

1 flags
  • Nylig endring 2026-02-23 Adresseendring registrert 2026-02-23.

EIDKJOSEN INDUSTRIPARK AS is registered as a limited company in Tromsø, Troms with organisation number 954132080. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 1989. Registered share capital is NOK 536,000, divided into 6376 shares. The company's stated purpose is: “Eie og forvalte fast eiendom samt å drive aktiviteter som står i forbindelse med dette. Selskapet skal også kunne delta i andre selskaper med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 438,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 438,000
Equity
NOK 5.2m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns EIDKJOSEN INDUSTRIPARK AS?

NORDPLAST AS
EIDKJOSEN INDUSTRIPARK AS
NOK 2.2m rev. · NOK 438,000 profit

EIDKJOSEN INDUSTRIPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIDKJOSEN INDUSTRIPARK AS

Who owns EIDKJOSEN INDUSTRIPARK AS?

NORDPLAST AS is the largest registered owner, with 100.0%.

What is the revenue of EIDKJOSEN INDUSTRIPARK AS?

EIDKJOSEN INDUSTRIPARK AS had revenue of NOK 2.2m in 2025.

Where is EIDKJOSEN INDUSTRIPARK AS based?

EIDKJOSEN INDUSTRIPARK AS has its business address in Tromsø.

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.