biztrac. BETA
COMPANY REGISTER PROFILE
933175499 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

VENARI EIENDOM AS

Org. no. 933175499 Limited company (AS) Porsgrunn Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 28,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

VENARI EIENDOM AS is registered as a limited company in Porsgrunn, Telemark with organisation number 933175499. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Eiendomsutvikling; kjøp og salg av eiendom og selskaper som eier eiendom, samt hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
▲ +18 %
Equity
NOK 28,000
▼ −34 %
Est. value
NOK 25,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-2.5%
Not satisfactory
Return on total assets
Solidity
5.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VENARI EIENDOM AS?

VENARI EIENDOM AS
NOK 0 rev. · NOK −14,000 profit

VENARI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VENARI EIENDOM AS

Who owns VENARI EIENDOM AS?

TORSHØLVEGEN 6 AS is the largest registered owner, with 100.0%.

What is the revenue of VENARI EIENDOM AS?

VENARI EIENDOM AS had revenue of NOK 0 in 2025.

Where is VENARI EIENDOM AS based?

VENARI EIENDOM AS has its business address in Porsgrunn.

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.