BIZTRAC BETA
Rental and operating of own or leased real estate

BYTOPPEN AS

Org. no. 928686884 Limited company (AS) Tromsø Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 303,000
Operating profit NOK 77,000
Equity NOK 116,000
Incorporated 2022
Share capital NOK 30,000

BYTOPPEN AS is registered as a limited company in Tromsø, Troms with organisation number 928686884. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Eiendomsutvikling, herunder erverv av fast eiendom for videreutvikling, drift og utleie av fast eiendom og annen virksomhet som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 303,000 in revenue and NOK 77,000 in operating profit.

Key figures · 2025

Revenue
NOK 303,000
Operating profit
NOK 77,000
Equity
NOK 116,000
Est. value
NOK 274,000

Financial health · 2025

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

Who owns BYTOPPEN AS?

EWA JANINA ROBERTSEN
BYTOPPEN AS
NOK 303,000 rev. · NOK 77,000 profit

BYTOPPEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BYTOPPEN AS er morselskap for 2 datterselskaper:

Frequently asked questions about BYTOPPEN AS

Who owns BYTOPPEN AS?

EWA JANINA ROBERTSEN is the largest registered owner, with 100.0%.

What is the revenue of BYTOPPEN AS?

BYTOPPEN AS had revenue of NOK 303,000 in 2025.

Where is BYTOPPEN AS based?

BYTOPPEN AS has its business address in Tromsø.

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.