biztrac. BETA
COMPANY REGISTER PROFILE
925984825 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Combined facilities support activities

SVEEN SERVICE AS

Org. no. 925984825 Limited company (AS) Vågå Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 54,000
Operating profit NOK −8,000
Equity NOK 37,000
Incorporated 2020
Share capital NOK 80,000

Signals

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

SVEEN SERVICE AS is registered as a limited company in Vågå, Innlandet with organisation number 925984825. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2020. Registered share capital is NOK 80,000, divided into 16 shares. The company's stated purpose is: “Servicetenester, tilrettelegging og småjobbar for hytter og hus; i dette utearbeid sumar og vinter, og elles anna som naturleg fell saman med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 54,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 54,000
▼ −21 %
Operating profit
NOK −8,000
▲ +63 %
Equity
NOK 37,000
▼ −18 %
Est. value
NOK 53,000

Financial health · 2025

Liquidity
-25.72
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
103.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SVEEN SERVICE AS?

SVEEN SERVICE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SVEEN SERVICE AS

Who owns SVEEN SERVICE AS?

Halvor Gården Sveen is the largest registered owner, with 37.5%.

What is the revenue of SVEEN SERVICE AS?

SVEEN SERVICE AS had revenue of NOK 54,000 in 2025.

Where is SVEEN SERVICE AS based?

SVEEN SERVICE AS has its business address in Vågå.

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.