BIZTRAC BETA
Rental and operating of own or leased real estate

TERMINALVEIEN 7 BERKÅK AS

Org. no. 921961774 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK 2.5m
Equity NOK 52.4m
Incorporated 2018
Share capital NOK 3.0m

TERMINALVEIEN 7 BERKÅK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921961774. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 3.0m, divided into 3000 shares. The company's stated purpose is: “Eie, utvikle, drifte og leie ut fast eiendom, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK 2.5m
Equity
NOK 52.4m
Est. value
NOK 44.0m

Financial health · 2024

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

Who owns TERMINALVEIEN 7 BERKÅK AS?

ANEO RENEWABLES HOLDING AS
TERMINALVEIEN 7 BERKÅK AS
NOK 7.1m rev. · NOK 2.5m profit

TERMINALVEIEN 7 BERKÅK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TERMINALVEIEN 7 BERKÅK AS

Who owns TERMINALVEIEN 7 BERKÅK AS?

ANEO RENEWABLES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TERMINALVEIEN 7 BERKÅK AS?

TERMINALVEIEN 7 BERKÅK AS had revenue of NOK 7.1m in 2024.

Who is the general manager of TERMINALVEIEN 7 BERKÅK AS?

Maria Haugdal is registered as general manager of TERMINALVEIEN 7 BERKÅK AS.

Where is TERMINALVEIEN 7 BERKÅK AS based?

TERMINALVEIEN 7 BERKÅK 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.