BIZTRAC BETA
Steam and air conditioning supply

SPIKKESTAD NÆRVARME AS

Org. no. 915255302 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −22,000
Equity NOK 389,000
Incorporated 2015
Share capital NOK 500,000

Signals

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

SPIKKESTAD NÆRVARME AS is registered as a limited company in Asker, Akershus with organisation number 915255302. The business is classified under steam and air conditioning supply (NACE 35.300). The company was incorporated in 2015. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Produksjon og salg av energi og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −22,000
Equity
NOK 389,000
Est. value
NOK 428,000

Financial health · 2025

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

Who owns SPIKKESTAD NÆRVARME AS?

TOR OLIVER GJERSØYEN
SPIKKESTAD NÆRVARME AS
NOK 0 rev. · NOK −22,000 profit

SPIKKESTAD NÆRVARME AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPIKKESTAD NÆRVARME AS

Who owns SPIKKESTAD NÆRVARME AS?

TOR OLIVER GJERSØYEN is the largest registered owner, with 38.0%.

What is the revenue of SPIKKESTAD NÆRVARME AS?

SPIKKESTAD NÆRVARME AS had revenue of NOK 0 in 2025.

Who is the general manager of SPIKKESTAD NÆRVARME AS?

Odd Kristian Kjos is registered as general manager of SPIKKESTAD NÆRVARME AS.

Where is SPIKKESTAD NÆRVARME AS based?

SPIKKESTAD NÆRVARME AS has its business address in Spikkestad.

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.