BIZTRAC BETA
Construction of residential and non-residential buildings

SVER Å JOBBA AS

Org. no. 929156528 Limited company (AS) Øygarden Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 121,000
Operating profit NOK −4,000
Equity NOK 28,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

SVER Å JOBBA AS is registered as a limited company in Øygarden, Vestland with organisation number 929156528. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Håndverkstjenester og konsulentvirksomhet innenfor byggfag.”. The most recent filed accounts, for the 2025 financial year, show NOK 121,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 121,000
Operating profit
NOK −4,000
Equity
NOK 28,000
Est. value
NOK 54,000

Financial health · 2025

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

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

Who owns SVER Å JOBBA AS?

MAGNAR TURØY
SVER Å JOBBA AS
NOK 121,000 rev. · NOK −4,000 profit

SVER Å JOBBA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SVER Å JOBBA AS

Who owns SVER Å JOBBA AS?

MAGNAR TURØY is the largest registered owner, with 50.0%.

What is the revenue of SVER Å JOBBA AS?

SVER Å JOBBA AS had revenue of NOK 121,000 in 2025.

Who is the general manager of SVER Å JOBBA AS?

Johnny Dyrkolbotn is registered as general manager of SVER Å JOBBA AS.

Where is SVER Å JOBBA AS based?

SVER Å JOBBA AS has its business address in Ågotnes.

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.