BIZTRAC BETA
Cutting, shaping and finishing of stone

STEINSERVICE ØSTFOLD AS

Org. no. 995542439 Limited company (AS) Halden Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 233,000
Equity NOK 1.5m
Incorporated 2010
Share capital NOK 250,000

STEINSERVICE ØSTFOLD AS is registered as a limited company in Halden, Østfold with organisation number 995542439. The business is classified under cutting, shaping and finishing of stone (NACE 23.700). The company was incorporated in 2010. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Salg og montering av nye gravsteiner og andre steinprodukter, sette navn på eksisterende steiner og drive med rehabilitering og annet arbeid på kirkegårdene.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 233,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 233,000
Equity
NOK 1.5m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns STEINSERVICE ØSTFOLD AS?

ULF VEGAR JAKOBSEN
STEINSERVICE ØSTFOLD AS
NOK 3.0m rev. · NOK 233,000 profit

STEINSERVICE ØSTFOLD AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about STEINSERVICE ØSTFOLD AS

Who owns STEINSERVICE ØSTFOLD AS?

ULF VEGAR JAKOBSEN is the largest registered owner, with 20.0%.

What is the revenue of STEINSERVICE ØSTFOLD AS?

STEINSERVICE ØSTFOLD AS had revenue of NOK 3.0m in 2024.

Who is the general manager of STEINSERVICE ØSTFOLD AS?

Bjørn Ove Greff is registered as general manager of STEINSERVICE ØSTFOLD AS.

Where is STEINSERVICE ØSTFOLD AS based?

STEINSERVICE ØSTFOLD AS has its business address in Halden.

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.