biztrac. BETA
COMPANY REGISTER PROFILE
935329434 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

SPETALS VERK HOLDING AS

Org. no. 935329434 Limited company (AS) Kongsvinger Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −55,000
Equity NOK 17.8m
Incorporated 2025
Share capital NOK 78,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−55k kr).
  • Nylig endring 2026-09-02 Aksjekapital registrert 2026-09-02.

SPETALS VERK HOLDING AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 935329434. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2025. Registered share capital is NOK 78,000, divided into 39 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer. I tillegg hva styret finner interessant for selskapet.”.

Key figures · 2025

Operating profit
NOK −55,000
Equity
NOK 17.8m
Est. value
NOK 78.5m

Financial health · 2025

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

Who owns SPETALS VERK HOLDING AS?

SPETALS VERK HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does SPETALS VERK HOLDING AS own?

SPETALS VERK HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SPETALS VERK HOLDING AS

Who owns SPETALS VERK HOLDING AS?

Eivind Magnus Jonassen is the largest registered owner, with 34.0%.

Who is the general manager of SPETALS VERK HOLDING AS?

Eivind Magnus Jonassen is registered as general manager of SPETALS VERK HOLDING AS.

Where is SPETALS VERK HOLDING AS based?

SPETALS VERK HOLDING AS has its business address in Kongsvinger.

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.