BIZTRAC BETA
COMPANY REGISTER PROFILE
928795128 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Site preparation

SOGN ANLEGGSTJENESTER AS

Org. no. 928795128 Limited company (AS) Sogndal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 474,000
Operating profit NOK −906
Equity NOK 34,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

SOGN ANLEGGSTJENESTER AS is registered as a limited company in Sogndal, Vestland with organisation number 928795128. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleige av eigen arbeidskraft til anlegg/landbruk.”. The most recent filed accounts, for the 2024 financial year, show NOK 474,000 in revenue and NOK −906 in operating profit.

Key figures · 2024

Revenue
NOK 474,000
Operating profit
NOK −906
Equity
NOK 34,000
Est. value
NOK 104,000

Financial health · 2024

Liquidity
1.48
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.3%
Weak
Equity as a share of total capital

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

Who owns SOGN ANLEGGSTJENESTER AS?

INGVAR JOSTEIN MYKLEBUST
SOGN ANLEGGSTJENESTER AS
NOK 474,000 rev. · NOK −906 profit

SOGN ANLEGGSTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOGN ANLEGGSTJENESTER AS

Who owns SOGN ANLEGGSTJENESTER AS?

INGVAR JOSTEIN MYKLEBUST is the largest registered owner, with 100.0%.

What is the revenue of SOGN ANLEGGSTJENESTER AS?

SOGN ANLEGGSTJENESTER AS had revenue of NOK 474,000 in 2024.

Where is SOGN ANLEGGSTJENESTER AS based?

SOGN ANLEGGSTJENESTER AS has its business address in Kaupanger.

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.