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

VISA EIENDOM AS

Org. no. 979637640 Limited company (AS) Strand Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 10.8m
Operating profit NOK 4.7m
Equity NOK 2.3m
Incorporated 1998
Share capital NOK 250,000

VISA EIENDOM AS is registered as a limited company in Strand, Rogaland with organisation number 979637640. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Eie og forvalte eiendommen Maskinveien 9 i Stavanger og hva som står i forbindelse dermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.8m in revenue and NOK 4.7m in operating profit.

Former names: OSJORD EIENDOM AS, HODNE TRADING AS

Key figures · 2025

Revenue
NOK 10.8m
▲ +9 %
Operating profit
NOK 4.7m
▲ +26 %
Equity
NOK 2.3m
▼ −77 %
Est. value
NOK 8.9m

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
9.6%
Satisfactory
Return on total assets
Solidity
4.0%
Weak
Equity as a share of total capital

Who owns VISA EIENDOM AS?

VISA EIENDOM AS
NOK 10.8m rev. · NOK 4.7m profit

VISA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VISA EIENDOM AS

Who owns VISA EIENDOM AS?

BORKE AS is the largest registered owner, with 100.0%.

What is the revenue of VISA EIENDOM AS?

VISA EIENDOM AS had revenue of NOK 10.8m in 2025.

Who is the general manager of VISA EIENDOM AS?

Børge Kverneland is registered as general manager of VISA EIENDOM AS.

Where is VISA EIENDOM AS based?

VISA EIENDOM AS has its business address in Tau.

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.