BIZTRAC BETA
Rental and operating of own or leased real estate

SPITEN INVEST AS

Org. no. 922851808 Limited company (AS) Kongsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −62,000
Equity NOK 3.6m
Incorporated 2019
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−62k kr).

SPITEN INVEST AS is registered as a limited company in Kongsberg, Buskerud with organisation number 922851808. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 300 shares. The company's stated purpose is: “Erverv, drift, utleie og eventuelt salg av fast eiendom samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −62,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −62,000
Equity
NOK 3.6m
Est. value
NOK 6.3m

Financial health · 2024

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

Who owns SPITEN INVEST AS?

GARD SPITEN
SPITEN INVEST AS
NOK 0 rev. · NOK −62,000 profit

SPITEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SPITEN INVEST AS own?

SPITEN INVEST AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SPITEN INVEST AS

Who owns SPITEN INVEST AS?

GARD SPITEN is the largest registered owner, with 100.0%.

What is the revenue of SPITEN INVEST AS?

SPITEN INVEST AS had revenue of NOK 0 in 2024.

Where is SPITEN INVEST AS based?

SPITEN INVEST AS has its business address in Kongsberg.

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.