biztrac. BETA
COMPANY REGISTER PROFILE
913001583 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

GAMLE LEIRDALSVEI 20 AS

Org. no. 913001583 Limited company (AS) Oslo Incorporated 1930 Active
Ownership graph ↗
Revenue 2025 NOK 12.9m
Operating profit NOK 10.4m
Equity NOK 2.4m
Incorporated 1930
Share capital NOK 800,000

GAMLE LEIRDALSVEI 20 AS is registered as a limited company in Oslo, Oslo with organisation number 913001583. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1930. Registered share capital is NOK 800,000, divided into 800000 shares. The company's stated purpose is: “Eie, utvikle og investere i fast eiendom, samt det som står i naturlig forbindelse med dette, herunder drift og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.9m in revenue and NOK 10.4m in operating profit.

Former names: AUG ISENE AS

Key figures · 2025

Revenue
NOK 12.9m
▲ +45 %
Operating profit
NOK 10.4m
▲ +87 %
Equity
NOK 2.4m
▼ −32 %
Est. value
NOK 13.4m

Financial health · 2025

Liquidity
0.73
Weak
Current assets ÷ current liabilities
Profitability
13.2%
Good
Return on total assets
Solidity
2.9%
Not satisfactory
Equity as a share of total capital

Who owns GAMLE LEIRDALSVEI 20 AS?

GAMLE LEIRDALSVEI 20 AS
NOK 12.9m rev. · NOK 10.4m profit

GAMLE LEIRDALSVEI 20 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAMLE LEIRDALSVEI 20 AS

Who owns GAMLE LEIRDALSVEI 20 AS?

FOKUS EIENDOMSFOND NORGE I HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GAMLE LEIRDALSVEI 20 AS?

GAMLE LEIRDALSVEI 20 AS had revenue of NOK 12.9m in 2025.

Where is GAMLE LEIRDALSVEI 20 AS based?

GAMLE LEIRDALSVEI 20 AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.