BIZTRAC BETA
Site preparation

STEIN OG JORD DEPONI AS

Org. no. 990447144 Limited company (AS) Indre Østfold Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 18.2m
Operating profit NOK 2.5m
Equity NOK 3.3m
Incorporated 2006
Share capital NOK 30,000

STEIN OG JORD DEPONI AS is registered as a limited company in Indre Østfold, Østfold with organisation number 990447144. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Maskinentreprenør, massedeponering, agentur og handel, produksjon, transport, kjøp og drift og salg av fast eiendom, og alt som er naturlig i forbindelse med dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.2m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 18.2m
Operating profit
NOK 2.5m
Equity
NOK 3.3m
Est. value
NOK 8.6m

Financial health · 2024

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.2%
Good
Equity as a share of total capital

Who owns STEIN OG JORD DEPONI AS?

IVAR ANDERSEN
STEIN OG JORD DEPONI AS
NOK 18.2m rev. · NOK 2.5m profit

STEIN OG JORD DEPONI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STEIN OG JORD DEPONI AS

Who owns STEIN OG JORD DEPONI AS?

IVAR ANDERSEN is the largest registered owner, with 50.0%.

What is the revenue of STEIN OG JORD DEPONI AS?

STEIN OG JORD DEPONI AS had revenue of NOK 18.2m in 2024.

Who is the general manager of STEIN OG JORD DEPONI AS?

Håkon Andersen is registered as general manager of STEIN OG JORD DEPONI AS.

Where is STEIN OG JORD DEPONI AS based?

STEIN OG JORD DEPONI AS has its business address in Spydeberg.

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.