BIZTRAC BETA
Rental and operating of own or leased real estate

VITAL JESSHEIM AS

Org. no. 929616359 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 168,000
Operating profit NOK 101,000
Equity NOK 219,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

VITAL JESSHEIM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929616359. 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 30 shares. The company's stated purpose is: “Eiendomsvirksomhet herunder utleie og annen økonomisk virksomhet, som også omfatter deltagelse i andre selskaper ved aksjeinnskudd eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 168,000 in revenue and NOK 101,000 in operating profit.

Key figures · 2024

Revenue
NOK 168,000
Operating profit
NOK 101,000
Equity
NOK 219,000
Est. value
NOK 345,000

Financial health · 2024

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

Who owns VITAL JESSHEIM AS?

VITAL INVEST AS
VITAL JESSHEIM AS
NOK 168,000 rev. · NOK 101,000 profit

VITAL JESSHEIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VITAL JESSHEIM AS

Who owns VITAL JESSHEIM AS?

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

What is the revenue of VITAL JESSHEIM AS?

VITAL JESSHEIM AS had revenue of NOK 168,000 in 2024.

Where is VITAL JESSHEIM AS based?

VITAL JESSHEIM AS has its business address in Trondheim.

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.