biztrac. BETA
COMPANY REGISTER PROFILE
866684472 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

OGNDALSVEGEN 117 AS

Org. no. 866684472 Limited company (AS) Meråker Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −66,000
Equity NOK 189,000
Incorporated 1993
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−66k kr).

OGNDALSVEGEN 117 AS is registered as a limited company in Meråker, Trøndelag with organisation number 866684472. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 200,000. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −66,000 in operating profit.

Former names: MOE HØISETH EIENDOM AS

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −66,000
▲ +30 %
Equity
NOK 189,000
▼ −5 %
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
-1.0%
Not satisfactory
Return on total assets
Solidity
17.0%
Satisfactory
Equity as a share of total capital

Who owns OGNDALSVEGEN 117 AS?

OGNDALSVEGEN 117 AS
NOK 0 rev. · NOK −66,000 profit

OGNDALSVEGEN 117 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OGNDALSVEGEN 117 AS

Who owns OGNDALSVEGEN 117 AS?

HØISETH HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OGNDALSVEGEN 117 AS?

OGNDALSVEGEN 117 AS had revenue of NOK 0 in 2025.

Where is OGNDALSVEGEN 117 AS based?

OGNDALSVEGEN 117 AS has its business address in Meråker.

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

Report a problem

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