BIZTRAC BETA
Rental and operating of own or leased real estate

NESET-EIENDOM AS

Org. no. 919822090 Limited company (AS) Frosta Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK −299,000
Equity NOK 1.1m
Incorporated 2017
Share capital NOK 1.1m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−299k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NESET-EIENDOM AS is registered as a limited company in Frosta, Trøndelag with organisation number 919822090. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 1.1m, divided into 1050 shares. The company's stated purpose is: “Forvaltning av kapital, kjøp, salg, utleie og forvaltning av eiendom, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK −299,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK −299,000
Equity
NOK 1.1m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns NESET-EIENDOM AS?

VIKEN - EIENDOM AS
NESET-EIENDOM AS
NOK 1.7m rev. · NOK −299,000 profit

NESET-EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESET-EIENDOM AS

Who owns NESET-EIENDOM AS?

VIKEN - EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of NESET-EIENDOM AS?

NESET-EIENDOM AS had revenue of NOK 1.7m in 2025.

Where is NESET-EIENDOM AS based?

NESET-EIENDOM AS has its business address in Frosta.

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.