BIZTRAC BETA
Rental and operating of own or leased real estate

ROALD AMUNDSENSVEG 1 B AS

Org. no. 834804662 Limited company (AS) Gjøvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 1.3m
Equity NOK 1.2m
Incorporated 2024
Share capital NOK 30,000

Signals

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

ROALD AMUNDSENSVEG 1 B AS is registered as a limited company in Gjøvik, Innlandet with organisation number 834804662. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøpe, selge, eie, leie ut, utvikle og drifte fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 1.3m
Equity
NOK 1.2m
Est. value
NOK 3.8m

Financial health · 2025

Liquidity
0.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.9%
Good
Equity as a share of total capital

Who owns ROALD AMUNDSENSVEG 1 B AS?

TEMA EIENDOM AS
ROALD AMUNDSENSVEG 1 B AS
NOK 2.3m rev. · NOK 1.3m profit

ROALD AMUNDSENSVEG 1 B AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROALD AMUNDSENSVEG 1 B AS

Who owns ROALD AMUNDSENSVEG 1 B AS?

TEMA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ROALD AMUNDSENSVEG 1 B AS?

ROALD AMUNDSENSVEG 1 B AS had revenue of NOK 2.3m in 2025.

Where is ROALD AMUNDSENSVEG 1 B AS based?

ROALD AMUNDSENSVEG 1 B 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.