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

ELIASMOEN 1 AS

Org. no. 918715886 Limited company (AS) Grong Incorporated 2017 Active
Revenue 2025 NOK 502,000
Operating profit NOK 222,000
Equity NOK 344,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-24 Aksjekapital registrert 2026-07-24.

ELIASMOEN 1 AS is registered as a limited company in Grong, Trøndelag with organisation number 918715886. 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 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp, salg, utleie av fast eiendom og annet som naturlig faller sammen med dette, herunder delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 502,000 in revenue and NOK 222,000 in operating profit.

Key figures · 2025

Revenue
NOK 502,000
▲ +6 %
Operating profit
NOK 222,000
▲ +7 %
Equity
NOK 344,000
▲ +3 %
Est. value
NOK 451,000

Financial health · 2025

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
6.7%
Satisfactory
Return on total assets
Solidity
10.5%
Satisfactory
Equity as a share of total capital

Who owns ELIASMOEN 1 AS?

ELIASMOEN 1 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ELIASMOEN 1 AS

Who owns ELIASMOEN 1 AS?

Kurt Magnar Lande Melhus is the largest registered owner, with 33.3%.

What is the revenue of ELIASMOEN 1 AS?

ELIASMOEN 1 AS had revenue of NOK 502,000 in 2025.

Where is ELIASMOEN 1 AS based?

ELIASMOEN 1 AS has its business address in Grong.

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.