BIZTRAC BETA
COMPANY REGISTER PROFILE
921664907 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Site preparation

MYRAN MASKIN AS

Org. no. 921664907 Limited company (AS) Indre Fosen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 134,000
Operating profit NOK 6,000
Equity NOK −49,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−49k kr).

MYRAN MASKIN AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 921664907. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Maskinentreprenørvirksomhet innen landbruket.”. The most recent filed accounts, for the 2025 financial year, show NOK 134,000 in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 134,000
Operating profit
NOK 6,000
Equity
NOK −49,000
Est. value
NOK 26,000

Financial health · 2024

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-25.5%
Weak
Equity as a share of total capital

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

Who owns MYRAN MASKIN AS?

JOHANNES HIDLE
MYRAN MASKIN AS
NOK 134,000 rev. · NOK 6,000 profit

MYRAN MASKIN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MYRAN MASKIN AS

Who owns MYRAN MASKIN AS?

JOHANNES HIDLE is the largest registered owner, with 33.3%.

What is the revenue of MYRAN MASKIN AS?

MYRAN MASKIN AS had revenue of NOK 134,000 in 2025.

Who is the general manager of MYRAN MASKIN AS?

Jørgen Rødsjø is registered as general manager of MYRAN MASKIN AS.

Where is MYRAN MASKIN AS based?

MYRAN MASKIN AS has its business address in Verrabotn.

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.