biztrac. BETA
COMPANY REGISTER PROFILE
919594144 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Compulsory dissolution UPDATED 03.10.2026
⚠SPREK365 HOLDING AS is registered as “Compulsory dissolution” with the Brønnøysund Register Centre.
Uoppgitt

SPREK365 HOLDING AS

Org. no. 919594144 Limited company (AS) Giske Incorporated 2017 Compulsory dissolution
Operating profit NOK −145,000
Equity NOK 12.1m
Incorporated 2017
Share capital NOK 60,000

Signals

1 flags
  • Tvangsoppløsning Selskapet er under tvangsoppløsning.

SPREK365 HOLDING AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 919594144. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i verdipapirer og eiendom, drift av eiendom, salg av konsulent- og administrasjonstjenester, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2023

Operating profit
NOK −145,000
▲ +95 %
Equity
NOK 12.1m
▲ +12 %

Financial health · 2023

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

Who owns SPREK365 HOLDING AS?

SPREK365 HOLDING AS
· NOK −145,000 profit

SPREK365 HOLDING AS has 2 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Which companies does SPREK365 HOLDING AS own?

SPREK365 HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SPREK365 HOLDING AS

Who owns SPREK365 HOLDING AS?

Hans Arne Hjeldnes is the largest registered owner, with 50.0%.

Where is SPREK365 HOLDING AS based?

SPREK365 HOLDING AS has its business address in Vigra.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.