BIZTRAC BETA
COMPANY REGISTER PROFILE
997536851 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

ENGSET EIENDOM AS

Org. no. 997536851 Limited company (AS) Tolga Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 174,000
Operating profit NOK −22,000
Equity NOK −311,000
Incorporated 2011
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−311k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

ENGSET EIENDOM AS is registered as a limited company in Tolga, Innlandet with organisation number 997536851. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å eie, investere i og drive fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 174,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 174,000
▼ −42 %
Operating profit
NOK −22,000
▼ −136 %
Equity
NOK −311,000
▼ −8 %
Est. value
NOK 77,000

Financial health · 2025

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.9%
Not satisfactory
Return on total assets
Solidity
-12.4%
Weak
Equity as a share of total capital

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

Who owns ENGSET EIENDOM AS?

No shareholders are registered for ENGSET EIENDOM AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ENGSET EIENDOM AS

What is the revenue of ENGSET EIENDOM AS?

ENGSET EIENDOM AS had revenue of NOK 174,000 in 2025.

Where is ENGSET EIENDOM AS based?

ENGSET EIENDOM AS has its business address in Vingelen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.