BIZTRAC BETA
Buying and selling of own real estate

NYLUND EIENDOM AS

Org. no. 930016381 Limited company (AS) Lyngen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 106,000
Operating profit NOK 73,000
Equity NOK −171,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−171k kr).

NYLUND EIENDOM AS is registered as a limited company in Lyngen, Troms with organisation number 930016381. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eiendomsforvaltning. Utleie. Kjøp og salg.”. The most recent filed accounts, for the 2024 financial year, show NOK 106,000 in revenue and NOK 73,000 in operating profit.

Key figures · 2024

Revenue
NOK 106,000
Operating profit
NOK 73,000
Equity
NOK −171,000
Est. value
NOK 565,000

Financial health · 2024

Liquidity
71.57
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-103.9%
Weak
Equity as a share of total capital

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

Who owns NYLUND EIENDOM AS?

HÅVARD ANSTEIN KRISTIANSEN
NYLUND EIENDOM AS
NOK 106,000 rev. · NOK 73,000 profit

NYLUND EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NYLUND EIENDOM AS

Who owns NYLUND EIENDOM AS?

HÅVARD ANSTEIN KRISTIANSEN is the largest registered owner, with 33.3%.

What is the revenue of NYLUND EIENDOM AS?

NYLUND EIENDOM AS had revenue of NOK 106,000 in 2024.

Who is the general manager of NYLUND EIENDOM AS?

Håvard Anstein Kristiansen is registered as general manager of NYLUND EIENDOM AS.

Where is NYLUND EIENDOM AS based?

NYLUND EIENDOM AS has its business address in Svensby.

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.