BIZTRAC BETA
Other real estate activities on a fee or contract basis

VENNATRØ ØST AS

Org. no. 916901526 Limited company (AS) Stjørdal Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 2.3m
Equity NOK 29.0m
Incorporated 2016
Share capital NOK 35.5m

Signals

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

VENNATRØ ØST AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 916901526. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2016. Registered share capital is NOK 35.5m, divided into 1000 shares. The company's stated purpose is: “Eiendomsforvaltning samt hva derved står i forbindelse, herunder delta i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 2.3m
Equity
NOK 29.0m
Est. value
NOK 23.2m

Financial health · 2024

Liquidity
2.48
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.8%
Good
Equity as a share of total capital

Who owns VENNATRØ ØST AS?

VENNATRØ GRUPPEN AS
VENNATRØ ØST AS
NOK 2.3m rev. · NOK 2.3m profit

VENNATRØ ØST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VENNATRØ ØST AS own?

VENNATRØ ØST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VENNATRØ ØST AS

Who owns VENNATRØ ØST AS?

VENNATRØ GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of VENNATRØ ØST AS?

VENNATRØ ØST AS had revenue of NOK 2.3m in 2024.

Where is VENNATRØ ØST AS based?

VENNATRØ ØST AS has its business address in Stjørdal.

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.