BIZTRAC BETA
COMPANY REGISTER PROFILE
918066934 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other real estate activities on a fee or contract basis

BRANESVEGEN 2 AS

Org. no. 918066934 Limited company (AS) Levanger Incorporated 2016 Active
Ownership graph ↗
Equity NOK 30,000
Incorporated 2016
Share capital NOK 30,000

BRANESVEGEN 2 AS is registered as a limited company in Levanger, Trøndelag with organisation number 918066934. 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 30,000, divided into 30 shares. The company's stated purpose is: “Forvaltning og drift av eiendom.”.

Key figures · 2025

Equity
NOK 30,000
▲ +0 %
Est. value
NOK 27,000

Financial health · 2025

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.1%
Weak
Equity as a share of total capital

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

Who owns BRANESVEGEN 2 AS?

BRANESVEGEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRANESVEGEN 2 AS

Who owns BRANESVEGEN 2 AS?

PER KÅRE HJELMSTADBAKK is the largest registered owner, with 100.0%.

Who is the general manager of BRANESVEGEN 2 AS?

Per Kåre Hjelmstadbakk is registered as general manager of BRANESVEGEN 2 AS.

Where is BRANESVEGEN 2 AS based?

BRANESVEGEN 2 AS has its business address in Levanger.

Property

Business address Branesvegen 2, 7606 Levanger
Cadastral unit 5037-314/25/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.