BIZTRAC BETA
Construction of residential and non-residential buildings

SAGBAKK BYGGSERVICE AS

Org. no. 922161704 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 56,000
Equity NOK 31,000
Incorporated 2019
Share capital NOK 30,000

SAGBAKK BYGGSERVICE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922161704. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Annen spesialisert bygge- og anleggsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 56,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 56,000
Equity
NOK 31,000
Est. value
NOK 181,000

Financial health · 2024

Liquidity
0.71
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SAGBAKK BYGGSERVICE AS?

STEIN-ARVE SAGBAKK
SAGBAKK BYGGSERVICE AS
NOK 1.5m rev. · NOK 56,000 profit

SAGBAKK BYGGSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAGBAKK BYGGSERVICE AS

Who owns SAGBAKK BYGGSERVICE AS?

STEIN-ARVE SAGBAKK is the largest registered owner, with 100.0%.

What is the revenue of SAGBAKK BYGGSERVICE AS?

SAGBAKK BYGGSERVICE AS had revenue of NOK 1.5m in 2025.

Who is the general manager of SAGBAKK BYGGSERVICE AS?

Stein-Arve Sagbakk is registered as general manager of SAGBAKK BYGGSERVICE AS.

Where is SAGBAKK BYGGSERVICE AS based?

SAGBAKK BYGGSERVICE AS has its business address in Heimdal.

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.