BIZTRAC BETA
Rental and operating of own or leased real estate

GAMLE GLENG AS

Org. no. 914435781 Limited company (AS) Sarpsborg Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 750,000
Operating profit NOK 3,000
Equity NOK 1.1m
Incorporated 1985
Share capital NOK 100,000

Signals

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

GAMLE GLENG AS is registered as a limited company in Sarpsborg, Østfold with organisation number 914435781. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1985. Registered share capital is NOK 100,000. The company's stated purpose is: “Kjøpe, eie, selge og forvalte fast eiendom, deltagelse i andre selskaper samt det som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 750,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2025

Revenue
NOK 750,000
Operating profit
NOK 3,000
Equity
NOK 1.1m
Est. value
NOK 735,000

Financial health · 2025

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

Who owns GAMLE GLENG AS?

SØRLIE GRUPPEN AS
GAMLE GLENG AS
NOK 750,000 rev. · NOK 3,000 profit

GAMLE GLENG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GAMLE GLENG AS

Who owns GAMLE GLENG AS?

SØRLIE GRUPPEN AS is the largest registered owner, with 70.0%.

What is the revenue of GAMLE GLENG AS?

GAMLE GLENG AS had revenue of NOK 750,000 in 2025.

Who is the general manager of GAMLE GLENG AS?

Terje Asbjørn Klavestad is registered as general manager of GAMLE GLENG AS.

Where is GAMLE GLENG AS based?

GAMLE GLENG AS has its business address in Sarpsborg.

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.