BIZTRAC BETA
Repair and maintenance of machinery

ENSRUD MASKIN OG INDUSTRISERVICE AS

Org. no. 933711218 Limited company (AS) Trysil Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 21,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4k kr).

ENSRUD MASKIN OG INDUSTRISERVICE AS is registered as a limited company in Trysil, Innlandet with organisation number 933711218. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen reparasjon av maskiner - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures · 2024

Operating profit
NOK −4,000
Equity
NOK 21,000
Est. value
NOK 24,000

Financial health · 2024

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

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

Who owns ENSRUD MASKIN OG INDUSTRISERVICE AS?

VEGARD ENSRUD
ENSRUD MASKIN OG INDUSTRISERVICE AS
· NOK −4,000 profit

ENSRUD MASKIN OG INDUSTRISERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENSRUD MASKIN OG INDUSTRISERVICE AS

Who owns ENSRUD MASKIN OG INDUSTRISERVICE AS?

VEGARD ENSRUD is the largest registered owner, with 100.0%.

Who is the general manager of ENSRUD MASKIN OG INDUSTRISERVICE AS?

Vegard Ensrud is registered as general manager of ENSRUD MASKIN OG INDUSTRISERVICE AS.

Where is ENSRUD MASKIN OG INDUSTRISERVICE AS based?

ENSRUD MASKIN OG INDUSTRISERVICE AS has its business address in Søre Osen.

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.