BIZTRAC BETA
Rental and operating of own or leased real estate

S-LAGET AS

Org. no. 829589052 Limited company (AS) Etnedal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 383,000
Operating profit NOK 158,000
Equity NOK −65,000
Incorporated 2022
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−65k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

S-LAGET AS is registered as a limited company in Etnedal, Innlandet with organisation number 829589052. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eierskap og drift av eiendom, eie aksjer og andeler i andre selskaper, og det som har naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 383,000 in revenue and NOK 158,000 in operating profit.

Key figures · 2024

Revenue
NOK 383,000
Operating profit
NOK 158,000
Equity
NOK −65,000
Est. value
NOK 948,000

Financial health · 2024

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

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

Who owns S-LAGET AS?

INREGNICO AS
S-LAGET AS
NOK 383,000 rev. · NOK 158,000 profit

S-LAGET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about S-LAGET AS

Who owns S-LAGET AS?

INREGNICO AS is the largest registered owner, with 70.0%.

What is the revenue of S-LAGET AS?

S-LAGET AS had revenue of NOK 383,000 in 2024.

Where is S-LAGET AS based?

S-LAGET AS has its business address in Etnedal.

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.