BIZTRAC BETA
Development of building projects

GAMMELSAGA UTVIKLING AS

Org. no. 917848181 Limited company (AS) Namsos Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 240,000
Operating profit NOK −573,000
Equity NOK 558,000
Incorporated 2016
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−573k kr).

GAMMELSAGA UTVIKLING AS is registered as a limited company in Namsos, Trøndelag with organisation number 917848181. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Utvikling og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 240,000 in revenue and NOK −573,000 in operating profit.

Key figures · 2025

Revenue
NOK 240,000
Operating profit
NOK −573,000
Equity
NOK 558,000
Est. value
NOK 742,000

Financial health · 2025

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

Who owns GAMMELSAGA UTVIKLING AS?

BRÅHOLMEN EIENDOM AS
GAMMELSAGA UTVIKLING AS
NOK 240,000 rev. · NOK −573,000 profit

GAMMELSAGA UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GAMMELSAGA UTVIKLING AS

Who owns GAMMELSAGA UTVIKLING AS?

BRÅHOLMEN EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of GAMMELSAGA UTVIKLING AS?

GAMMELSAGA UTVIKLING AS had revenue of NOK 240,000 in 2025.

Who is the general manager of GAMMELSAGA UTVIKLING AS?

Ole Rogstad Jørstad is registered as general manager of GAMMELSAGA UTVIKLING AS.

Where is GAMMELSAGA UTVIKLING AS based?

GAMMELSAGA UTVIKLING AS has its business address in Namsos.

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.