BIZTRAC BETA
Rental and operating of own or leased real estate

VIKENTE EIENDOM AS

Org. no. 930890332 Limited company (AS) Øvre Eiker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 540,000
Operating profit NOK 462,000
Equity NOK 257,000
Incorporated 2022
Share capital NOK 32,000

Signals

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

VIKENTE EIENDOM AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 930890332. 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 32,000, divided into 3168224 shares. The company's stated purpose is: “Kjøp, salg, utvikling og drift av eiendommer, kjøp og salg av aksjer i andre selskaper, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 540,000 in revenue and NOK 462,000 in operating profit.

Key figures · 2025

Revenue
NOK 540,000
Operating profit
NOK 462,000
Equity
NOK 257,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.9%
Weak
Equity as a share of total capital

Who owns VIKENTE EIENDOM AS?

VIKENTE INVEST AS
VIKENTE EIENDOM AS
NOK 540,000 rev. · NOK 462,000 profit

VIKENTE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKENTE EIENDOM AS

Who owns VIKENTE EIENDOM AS?

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

What is the revenue of VIKENTE EIENDOM AS?

VIKENTE EIENDOM AS had revenue of NOK 540,000 in 2025.

Where is VIKENTE EIENDOM AS based?

VIKENTE EIENDOM AS has its business address in Fiskum.

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.