BIZTRAC BETA
COMPANY REGISTER PROFILE
920656943 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

HELGATUNTEIGEN II

Org. no. 920656943 Condominium flat owner (ESEK) Voss Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 265,000
Operating profit NOK 15,000
Equity NOK 415,000
Incorporated 2015

HELGATUNTEIGEN II is registered as a condominium flat owner in Voss, Vestland with organisation number 920656943. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2015. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 265,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2025

Revenue
NOK 265,000
Operating profit
NOK 15,000
Equity
NOK 415,000
Est. value
NOK 330,000

Financial health · 2025

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

Who owns HELGATUNTEIGEN II?

No shareholders are registered for HELGATUNTEIGEN II in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HELGATUNTEIGEN II

What is the revenue of HELGATUNTEIGEN II?

HELGATUNTEIGEN II had revenue of NOK 265,000 in 2025.

Where is HELGATUNTEIGEN II based?

HELGATUNTEIGEN II has its business address in Vossestrand.

Property

Business address Feissgrovvegen 183, 5713 Vossestrand
Cadastral unit 4621-273/44/0/0
Building Hytter, sommerhus ol fritidsbygning · 10 units

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.