BIZTRAC BETA
Rental and operating of own or leased real estate

LYNG1 EIENDOM AS

Org. no. 931718339 Limited company (AS) Lyngen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 528,000
Operating profit NOK 144,000
Equity NOK 906
Incorporated 2023
Share capital NOK 30,000

LYNG1 EIENDOM AS is registered as a limited company in Lyngen, Troms with organisation number 931718339. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Erverve og leie ut fast eiendom og driftsløsøre. Utføre transport av varer og tjenester. Utleie av kjøretøy og varehengere.”. The most recent filed accounts, for the 2024 financial year, show NOK 528,000 in revenue and NOK 144,000 in operating profit.

Key figures · 2024

Revenue
NOK 528,000
Operating profit
NOK 144,000
Equity
NOK 906
Est. value
NOK 285,000

Financial health · 2024

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

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

Who owns LYNG1 EIENDOM AS?

HANNE KAROLINE KRÆMER
LYNG1 EIENDOM AS
NOK 528,000 rev. · NOK 144,000 profit

LYNG1 EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LYNG1 EIENDOM AS own?

LYNG1 EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LYNG1 EIENDOM AS

Who owns LYNG1 EIENDOM AS?

HANNE KAROLINE KRÆMER is the largest registered owner, with 33.3%.

What is the revenue of LYNG1 EIENDOM AS?

LYNG1 EIENDOM AS had revenue of NOK 528,000 in 2024.

Where is LYNG1 EIENDOM AS based?

LYNG1 EIENDOM AS has its business address in Lyngseidet.

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.