BIZTRAC BETA
Construction of residential and non-residential buildings

STENE TØMRERSERVICE AS

Org. no. 992779098 Limited company (AS) Frosta Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 13.9m
Operating profit NOK 883,000
Equity NOK 1.0m
Incorporated 2008
Employees 9
Share capital NOK 100,000

STENE TØMRERSERVICE AS is registered as a limited company in Frosta, Trøndelag with organisation number 992779098. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Oppføring av bygninger og andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.9m in revenue and NOK 883,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.9m
Operating profit
NOK 883,000
Equity
NOK 1.0m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns STENE TØMRERSERVICE AS?

MARKUS BOTTEN
STENE TØMRERSERVICE AS
NOK 13.9m rev. · NOK 883,000 profit

STENE TØMRERSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STENE TØMRERSERVICE AS

Who owns STENE TØMRERSERVICE AS?

MARKUS BOTTEN is the largest registered owner, with 50.0%.

What is the revenue of STENE TØMRERSERVICE AS?

STENE TØMRERSERVICE AS had revenue of NOK 13.9m in 2025.

Who is the general manager of STENE TØMRERSERVICE AS?

Stein Ola Stene is registered as general manager of STENE TØMRERSERVICE AS.

Where is STENE TØMRERSERVICE AS based?

STENE TØMRERSERVICE AS has its business address in Frosta.

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.