BIZTRAC BETA
Rental and operating of own or leased real estate

NE14 EIENDOM AS

Org. no. 923450173 Limited company (AS) Kristiansund Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 875,000
Operating profit NOK 170,000
Equity NOK 516,000
Incorporated 2019
Share capital NOK 530,000

NE14 EIENDOM AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 923450173. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 530,000, divided into 5300 shares. The company's stated purpose is: “Ervervelse og utvikling av tomter og eiendommer for utleie og salg, samt drive slik aktivitet som naturlig faller innunder dette, herunder å eie andeler i andre selskapet med tilsvarende aktivitet.”. The most recent filed accounts, for the 2024 financial year, show NOK 875,000 in revenue and NOK 170,000 in operating profit.

Key figures · 2024

Revenue
NOK 875,000
Operating profit
NOK 170,000
Equity
NOK 516,000
Est. value
NOK 644,000

Financial health · 2024

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

Who owns NE14 EIENDOM AS?

ZIKO GRUPPEN AS
NE14 EIENDOM AS
NOK 875,000 rev. · NOK 170,000 profit

NE14 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NE14 EIENDOM AS

Who owns NE14 EIENDOM AS?

ZIKO GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of NE14 EIENDOM AS?

NE14 EIENDOM AS had revenue of NOK 875,000 in 2024.

Who is the general manager of NE14 EIENDOM AS?

Espen Bugge Larssen is registered as general manager of NE14 EIENDOM AS.

Where is NE14 EIENDOM AS based?

NE14 EIENDOM AS has its business address in Kristiansund N.

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.