BIZTRAC BETA
Rental and operating of own or leased real estate

RAMBEKKVEGEN 3B AS

Org. no. 911992183 Limited company (AS) Gjøvik Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 908,000
Equity NOK 1.3m
Incorporated 2013
Share capital NOK 255,000

RAMBEKKVEGEN 3B AS is registered as a limited company in Gjøvik, Innlandet with organisation number 911992183. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 255,000, divided into 1 shares. The company's stated purpose is: “Eie og forvalte eiendommmen gnr 59, bnr 194 I Gjøvik kommune, samt annen økonomisk virksomhet, herunder investeringer i aksjer, fast eiendom og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 908,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 908,000
Equity
NOK 1.3m
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
7.34
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.1%
Satisfactory
Equity as a share of total capital

Who owns RAMBEKKVEGEN 3B AS?

TAFF INVEST AS
RAMBEKKVEGEN 3B AS
NOK 1.5m rev. · NOK 908,000 profit

RAMBEKKVEGEN 3B AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAMBEKKVEGEN 3B AS

Who owns RAMBEKKVEGEN 3B AS?

TAFF INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of RAMBEKKVEGEN 3B AS?

RAMBEKKVEGEN 3B AS had revenue of NOK 1.5m in 2025.

Who is the general manager of RAMBEKKVEGEN 3B AS?

Tom André Fazzi-Fjeldstad is registered as general manager of RAMBEKKVEGEN 3B AS.

Where is RAMBEKKVEGEN 3B AS based?

RAMBEKKVEGEN 3B 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 15.06.2026.

Report a problem

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