BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

JK SERVICE GEILO AS

Org. no. 913080130 Limited company (AS) Hol Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −70,000
Equity NOK 855,000
Incorporated 2014
Share capital NOK 984,000

Signals

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

JK SERVICE GEILO AS is registered as a limited company in Hol, Buskerud with organisation number 913080130. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2014. Registered share capital is NOK 984,000, divided into 32800 shares. The company's stated purpose is: “Kjøp, salg og utleie av maskiner og utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −70,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −70,000
Equity
NOK 855,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns JK SERVICE GEILO AS?

JK INVEST AS
JK SERVICE GEILO AS
NOK 1.1m rev. · NOK −70,000 profit

JK SERVICE GEILO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JK SERVICE GEILO AS

Who owns JK SERVICE GEILO AS?

JK INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of JK SERVICE GEILO AS?

JK SERVICE GEILO AS had revenue of NOK 1.1m in 2025.

Who is the general manager of JK SERVICE GEILO AS?

Johnny Kaupang is registered as general manager of JK SERVICE GEILO AS.

Where is JK SERVICE GEILO AS based?

JK SERVICE GEILO AS has its business address in Geilo.

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.