BIZTRAC BETA
Rental and operating of own or leased real estate

HELIE EIGEDOM AS

Org. no. 917882363 Limited company (AS) Voss Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 431,000
Operating profit NOK 183,000
Equity NOK −1.5m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,5 mill kr).

HELIE EIGEDOM AS is registered as a limited company in Voss, Vestland with organisation number 917882363. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eige, leige ut, kjøpa og selja eigedom, samt det som naturleg høyrer til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 431,000 in revenue and NOK 183,000 in operating profit.

Key figures · 2025

Revenue
NOK 431,000
Operating profit
NOK 183,000
Equity
NOK −1.5m
Est. value
NOK 1.3m

Financial health · 2025

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

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

Who owns HELIE EIGEDOM AS?

BRYNJULV LIE
HELIE EIGEDOM AS
NOK 431,000 rev. · NOK 183,000 profit

HELIE EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELIE EIGEDOM AS

Who owns HELIE EIGEDOM AS?

BRYNJULV LIE is the largest registered owner, with 100.0%.

What is the revenue of HELIE EIGEDOM AS?

HELIE EIGEDOM AS had revenue of NOK 431,000 in 2025.

Who is the general manager of HELIE EIGEDOM AS?

Brynjulv Lie is registered as general manager of HELIE EIGEDOM AS.

Where is HELIE EIGEDOM AS based?

HELIE EIGEDOM AS has its business address in Voss.

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.