BIZTRAC BETA
Combined facilities support activities

KP SERVICE NORD AS

Org. no. 916027699 Limited company (AS) Hamarøy Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −60,000
Equity NOK 266,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−60k kr).

KP SERVICE NORD AS is registered as a limited company in Hamarøy, Nordland with organisation number 916027699. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Vaktmestertjenester, reparasjoner, maritime tjenester, frisørvirksomhet og kjøp og salg mv.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −60,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −60,000
Equity
NOK 266,000
Est. value
NOK 907,000

Financial health · 2025

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

Who owns KP SERVICE NORD AS?

KINE JEANETT PETTERSEN
KP SERVICE NORD AS
NOK 1.3m rev. · NOK −60,000 profit

KP SERVICE NORD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KP SERVICE NORD AS

Who owns KP SERVICE NORD AS?

KINE JEANETT PETTERSEN is the largest registered owner, with 50.0%.

What is the revenue of KP SERVICE NORD AS?

KP SERVICE NORD AS had revenue of NOK 1.3m in 2025.

Who is the general manager of KP SERVICE NORD AS?

Kine Jeanett Pettersen is registered as general manager of KP SERVICE NORD AS.

Where is KP SERVICE NORD AS based?

KP SERVICE NORD AS has its business address in Innhavet.

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.