BIZTRAC BETA
Other real estate activities on a fee or contract basis

GAMMELSETERLIA 5 II AS

Org. no. 917926506 Limited company (AS) Molde Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 1.7m
Equity NOK 760,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GAMMELSETERLIA 5 II AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 917926506. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie og forvalte fast eiendom samt aksjer i andre selskaper og alt som naturlig tilhører slik virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 1.7m
Equity
NOK 760,000
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns GAMMELSETERLIA 5 II AS?

LANGSET EIENDOM AS
GAMMELSETERLIA 5 II AS
NOK 2.2m rev. · NOK 1.7m profit

GAMMELSETERLIA 5 II AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAMMELSETERLIA 5 II AS

Who owns GAMMELSETERLIA 5 II AS?

LANGSET EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of GAMMELSETERLIA 5 II AS?

GAMMELSETERLIA 5 II AS had revenue of NOK 2.2m in 2024.

Where is GAMMELSETERLIA 5 II AS based?

GAMMELSETERLIA 5 II AS has its business address in Molde.

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.