biztrac. BETA
COMPANY REGISTER PROFILE
929511980 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

GAMLEVEIEN 4 AS

Org. no. 929511980 Limited company (AS) Drammen Incorporated 2022 Active
Revenue 2025 NOK 0
Operating profit NOK −59,000
Equity NOK 1.1m
Incorporated 2022
Share capital NOK 100,000

Signals

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

GAMLEVEIEN 4 AS is registered as a limited company in Drammen, Buskerud with organisation number 929511980. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i eiendom, aksjer og andre verdipapirer, samt annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −59,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −59,000
▼ −26 %
Equity
NOK 1.1m
▼ −5 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
5.83
Very good
Current assets ÷ current liabilities
Profitability
-4.4%
Not satisfactory
Return on total assets
Solidity
82.9%
Very good
Equity as a share of total capital

Who owns GAMLEVEIEN 4 AS?

GAMLEVEIEN 4 AS
NOK 0 rev. · NOK −59,000 profit

GAMLEVEIEN 4 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GAMLEVEIEN 4 AS

Who owns GAMLEVEIEN 4 AS?

MATH HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of GAMLEVEIEN 4 AS?

GAMLEVEIEN 4 AS had revenue of NOK 0 in 2025.

Who is the general manager of GAMLEVEIEN 4 AS?

Terje Ottesen is registered as general manager of GAMLEVEIEN 4 AS.

Where is GAMLEVEIEN 4 AS based?

GAMLEVEIEN 4 AS has its business address in Drammen.

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.