biztrac. BETA
COMPANY REGISTER PROFILE
915184170 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

SYSTAD ANLEGG AS

Org. no. 915184170 Limited company (AS) Lindesnes Incorporated 2015 Active
Revenue 2025 NOK 1.5m
Operating profit NOK −114,000
Equity NOK −2.3m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,3 mill kr).

SYSTAD ANLEGG AS is registered as a limited company in Lindesnes, Agder with organisation number 915184170. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Arbeid med gravemaskin, anleggsarbeider og øvrige håndverkertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −114,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▼ −22 %
Operating profit
NOK −114,000
▼ −161 %
Equity
NOK −2.3m
▼ −5 %

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
-24.4%
Not satisfactory
Return on total assets
Solidity
-510.7%
Weak
Equity as a share of total capital

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

Who owns SYSTAD ANLEGG AS?

SYSTAD ANLEGG AS
NOK 1.5m rev. · NOK −114,000 profit

SYSTAD ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYSTAD ANLEGG AS

Who owns SYSTAD ANLEGG AS?

Atle Systad is the largest registered owner, with 100.0%.

What is the revenue of SYSTAD ANLEGG AS?

SYSTAD ANLEGG AS had revenue of NOK 1.5m in 2025.

Who is the general manager of SYSTAD ANLEGG AS?

Atle Systad is registered as general manager of SYSTAD ANLEGG AS.

Where is SYSTAD ANLEGG AS based?

SYSTAD ANLEGG AS has its business address in Holum.

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.