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

SÆTRE ANLEGGSSERVICE AS

Org. no. 911709244 Limited company (AS) Sykkylven Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK −39,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−39k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

SÆTRE ANLEGGSSERVICE AS is registered as a limited company in Sykkylven, Møre og Romsdal with organisation number 911709244. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Leveranser av grave- og transporttjenester, tjenester til landbruk, tjenester vedrørende arealplanlegging og arealutvikling. Salg og videreformiding av tjenester og utstyr.”.

Key figures · 2024

Operating profit
NOK −6,000
Equity
NOK −39,000

Financial health · 2024

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

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

Who owns SÆTRE ANLEGGSSERVICE AS?

KJETIL LEIV SÆTRE
SÆTRE ANLEGGSSERVICE AS
· NOK −6,000 profit

SÆTRE ANLEGGSSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SÆTRE ANLEGGSSERVICE AS

Who owns SÆTRE ANLEGGSSERVICE AS?

KJETIL LEIV SÆTRE is the largest registered owner, with 50.0%.

Who is the general manager of SÆTRE ANLEGGSSERVICE AS?

Kjetil Leiv Sætre is registered as general manager of SÆTRE ANLEGGSSERVICE AS.

Where is SÆTRE ANLEGGSSERVICE AS based?

SÆTRE ANLEGGSSERVICE AS has its business address in Ikornnes.

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.