BIZTRAC BETA
Rental and operating of own or leased real estate

TØNSVIKVEIEN 518 AS

Org. no. 959458855 Limited company (AS) Tromsø Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 848,000
Equity NOK 2.1m
Incorporated 1990
Share capital NOK 378,000

TØNSVIKVEIEN 518 AS is registered as a limited company in Tromsø, Troms with organisation number 959458855. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1990. Registered share capital is NOK 378,000, divided into 252 shares. The company's stated purpose is: “Eie og drive fast eiendom samt hva hermed står i forbindelse, herunder delta direkte eller gjennom aksjeerverv i eiendomsdrift samt virksomheter som driver i naturlig tilknyttede bransjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 848,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 848,000
Equity
NOK 2.1m
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.4%
Satisfactory
Equity as a share of total capital

Who owns TØNSVIKVEIEN 518 AS?

KARLS EIENDOM AS
TØNSVIKVEIEN 518 AS
NOK 3.8m rev. · NOK 848,000 profit

TØNSVIKVEIEN 518 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TØNSVIKVEIEN 518 AS own?

TØNSVIKVEIEN 518 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TØNSVIKVEIEN 518 AS

Who owns TØNSVIKVEIEN 518 AS?

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

What is the revenue of TØNSVIKVEIEN 518 AS?

TØNSVIKVEIEN 518 AS had revenue of NOK 3.8m in 2025.

Where is TØNSVIKVEIEN 518 AS based?

TØNSVIKVEIEN 518 AS has its business address in Krokelvdalen.

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.