BIZTRAC BETA
Rental and operating of own or leased real estate

MINKEN NÆRINGSPARK 6 AS

Org. no. 997305167 Limited company (AS) Tromsø Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 61,000
Incorporated 2011
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MINKEN NÆRINGSPARK 6 AS is registered as a limited company in Tromsø, Troms with organisation number 997305167. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling, salg og utleie av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −16,000
Equity
NOK 61,000
Est. value
NOK 56,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MINKEN NÆRINGSPARK 6 AS?

BARLINDHAUG EIENDOM AS
MINKEN NÆRINGSPARK 6 AS
· NOK −16,000 profit

MINKEN NÆRINGSPARK 6 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

MINKEN NÆRINGSPARK 6 AS er morselskap for 3 datterselskaper:

Frequently asked questions about MINKEN NÆRINGSPARK 6 AS

Who owns MINKEN NÆRINGSPARK 6 AS?

BARLINDHAUG EIENDOM AS is the largest registered owner, with 100.0%.

Who is the general manager of MINKEN NÆRINGSPARK 6 AS?

Kjetil Strømseng Paulsen is registered as general manager of MINKEN NÆRINGSPARK 6 AS.

Where is MINKEN NÆRINGSPARK 6 AS based?

MINKEN NÆRINGSPARK 6 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.