BIZTRAC BETA
Uoppgitt

SPIRE INVEST AS

Org. no. 915712991 Limited company (AS) Harstad Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 63,000
Operating profit NOK −115,000
Equity NOK 2.8m
Incorporated 2015
Share capital NOK 820,000

Signals

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

SPIRE INVEST AS is registered as a limited company in Harstad, Troms with organisation number 915712991. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2015. Registered share capital is NOK 820,000, divided into 820 shares. The company's stated purpose is: “Eie og forvalte aksjer i andre selskap samt virksomhet som faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 63,000 in revenue and NOK −115,000 in operating profit.

Key figures · 2024

Revenue
NOK 63,000
Operating profit
NOK −115,000
Equity
NOK 2.8m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns SPIRE INVEST AS?

AUDUN KJELL ANDREASSEN
SPIRE INVEST AS
NOK 63,000 rev. · NOK −115,000 profit

SPIRE INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SPIRE INVEST AS own?

SPIRE INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SPIRE INVEST AS

Who owns SPIRE INVEST AS?

AUDUN KJELL ANDREASSEN is the largest registered owner, with 50.0%.

What is the revenue of SPIRE INVEST AS?

SPIRE INVEST AS had revenue of NOK 63,000 in 2024.

Who is the general manager of SPIRE INVEST AS?

Audun Kjell Andreassen is registered as general manager of SPIRE INVEST AS.

Where is SPIRE INVEST AS based?

SPIRE INVEST AS has its business address in Harstad.

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.