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

RAMBEKKVEIEN 2 AS

Org. no. 990648611 Limited company (AS) Gjøvik Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 1.7m
Equity NOK 8.7m
Incorporated 2006
Share capital NOK 100,000

RAMBEKKVEIEN 2 AS is registered as a limited company in Gjøvik, Innlandet with organisation number 990648611. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering og utleie av eiendom, investering i verdipapirer, samt eie av aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
▼ −15 %
Operating profit
NOK 1.7m
▼ −9 %
Equity
NOK 8.7m
▲ +9 %
Est. value
NOK 9.1m

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
7.5%
Satisfactory
Return on total assets
Solidity
36.0%
Good
Equity as a share of total capital

Who owns RAMBEKKVEIEN 2 AS?

RAMBEKKVEIEN 2 AS
NOK 3.0m rev. · NOK 1.7m profit

RAMBEKKVEIEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAMBEKKVEIEN 2 AS

Who owns RAMBEKKVEIEN 2 AS?

TEMA NÆRINGSBYGG AS is the largest registered owner, with 100.0%.

What is the revenue of RAMBEKKVEIEN 2 AS?

RAMBEKKVEIEN 2 AS had revenue of NOK 3.0m in 2025.

Who is the general manager of RAMBEKKVEIEN 2 AS?

Martin Rolf Zettervall is registered as general manager of RAMBEKKVEIEN 2 AS.

Where is RAMBEKKVEIEN 2 AS based?

RAMBEKKVEIEN 2 AS has its business address in Gjøvik.

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.