BIZTRAC BETA
Site preparation

SK ANLEGG AS

Org. no. 925450324 Limited company (AS) Notodden Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 16.0m
Operating profit NOK 1.8m
Equity NOK 1.4m
Incorporated 2020
Employees 13
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SK ANLEGG AS is registered as a limited company in Notodden, Telemark with organisation number 925450324. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020 and has 13 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Anleggsvirksomhet av ulik art hovedsakelig med gravemaskin og tilhørende maskiner, brøyting og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.0m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 16.0m
Operating profit
NOK 1.8m
Equity
NOK 1.4m
Est. value
NOK 6.0m

Financial health · 2024

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.9%
Good
Equity as a share of total capital

Who owns SK ANLEGG AS?

KAALI INVEST AS
SK ANLEGG AS
NOK 16.0m rev. · NOK 1.8m profit

SK ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SK ANLEGG AS

Who owns SK ANLEGG AS?

KAALI INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SK ANLEGG AS?

SK ANLEGG AS had revenue of NOK 16.0m in 2024.

Who is the general manager of SK ANLEGG AS?

Ingar Kaasa Kaali is registered as general manager of SK ANLEGG AS.

Where is SK ANLEGG AS based?

SK ANLEGG AS has its business address in Gransherad.

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.