BIZTRAC BETA
Masonry and bricklaying activities

STEINMILJØ AS

Org. no. 997722094 Limited company (AS) Moss Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 11.0m
Operating profit NOK −48,000
Equity NOK 2.7m
Incorporated 2011
Employees 6
Share capital NOK 100,000

Signals

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

STEINMILJØ AS is registered as a limited company in Moss, Østfold with organisation number 997722094. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2011 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av belegningsprodukter, utførelse av konsulenttjenester, samt betong og natursteinprodukter. Videre virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.0m in revenue and NOK −48,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.0m
Operating profit
NOK −48,000
Equity
NOK 2.7m
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns STEINMILJØ AS?

STEINMILJØ HOLDING AS
STEINMILJØ AS
NOK 11.0m rev. · NOK −48,000 profit

STEINMILJØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STEINMILJØ AS

Who owns STEINMILJØ AS?

STEINMILJØ HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STEINMILJØ AS?

STEINMILJØ AS had revenue of NOK 11.0m in 2024.

Who is the general manager of STEINMILJØ AS?

Espen Andreassen is registered as general manager of STEINMILJØ AS.

Where is STEINMILJØ AS based?

STEINMILJØ AS has its business address in Larkollen.

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.