BIZTRAC BETA
Construction of residential and non-residential buildings

SAGA BYGGENTREPRENØR AS

Org. no. 922018537 Limited company (AS) Færder Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 15.0m
Operating profit NOK −186,000
Equity NOK 1.1m
Incorporated 2018
Employees 6
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−186k kr).
  • Nylig endring 2026-07-21 Aksjekapital registrert 2026-07-21.

SAGA BYGGENTREPRENØR AS is registered as a limited company in Færder, Vestfold with organisation number 922018537. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018 and has 6 registered employees. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Oppføring av bygninger og tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.0m in revenue and NOK −186,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.0m
Operating profit
NOK −186,000
Equity
NOK 1.1m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns SAGA BYGGENTREPRENØR AS?

T.M. RØD HOLDING AS
SAGA BYGGENTREPRENØR AS
NOK 15.0m rev. · NOK −186,000 profit

SAGA BYGGENTREPRENØR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAGA BYGGENTREPRENØR AS

Who owns SAGA BYGGENTREPRENØR AS?

T.M. RØD HOLDING AS is the largest registered owner, with 47.0%.

What is the revenue of SAGA BYGGENTREPRENØR AS?

SAGA BYGGENTREPRENØR AS had revenue of NOK 15.0m in 2024.

Where is SAGA BYGGENTREPRENØR AS based?

SAGA BYGGENTREPRENØR AS has its business address in Skallestad.

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.