BIZTRAC BETA
Rental and operating of own or leased real estate

STL MASKIN AS

Org. no. 917591385 Limited company (AS) Nord-Fron Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 720,000
Operating profit NOK −38,000
Equity NOK 6.5m
Incorporated 2016
Share capital NOK 52,000

Signals

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

STL MASKIN AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 917591385. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 52,000, divided into 104 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer, andeler i selskap, fast eiendom, maskiner/utstyr og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 720,000 in revenue and NOK −38,000 in operating profit.

Key figures · 2024

Revenue
NOK 720,000
Operating profit
NOK −38,000
Equity
NOK 6.5m
Est. value
NOK 5.5m

Financial health · 2024

Liquidity
51.73
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
94.9%
Very good
Equity as a share of total capital

Who owns STL MASKIN AS?

STEIN ROGER LIUM
STL MASKIN AS
NOK 720,000 rev. · NOK −38,000 profit

STL MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STL MASKIN AS

Who owns STL MASKIN AS?

STEIN ROGER LIUM is the largest registered owner, with 50.0%.

What is the revenue of STL MASKIN AS?

STL MASKIN AS had revenue of NOK 720,000 in 2024.

Who is the general manager of STL MASKIN AS?

Stein Roger Lium is registered as general manager of STL MASKIN AS.

Where is STL MASKIN AS based?

STL MASKIN AS has its business address in Kvam.

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.