BIZTRAC BETA
Construction of residential and non-residential buildings

SKREIA TØMRERSERVICE AS

Org. no. 997216350 Limited company (AS) Østre Toten Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 422,000
Equity NOK 1.2m
Incorporated 2011
Share capital NOK 100,000

SKREIA TØMRERSERVICE AS is registered as a limited company in Østre Toten, Innlandet with organisation number 997216350. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bygge- og anleggsvirksomhet, herunder investeringer i og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 422,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 422,000
Equity
NOK 1.2m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns SKREIA TØMRERSERVICE AS?

KRISTIAN STUBBERUD
SKREIA TØMRERSERVICE AS
NOK 3.4m rev. · NOK 422,000 profit

SKREIA TØMRERSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKREIA TØMRERSERVICE AS

Who owns SKREIA TØMRERSERVICE AS?

KRISTIAN STUBBERUD is the largest registered owner, with 50.0%.

What is the revenue of SKREIA TØMRERSERVICE AS?

SKREIA TØMRERSERVICE AS had revenue of NOK 3.4m in 2025.

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

Kristian Stubberud is registered as general manager of SKREIA TØMRERSERVICE AS.

Where is SKREIA TØMRERSERVICE AS based?

SKREIA TØMRERSERVICE AS has its business address in Skreia.

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.