BIZTRAC BETA
Support activities for crop production

REMMAN MASKINDRIFT AS

Org. no. 913410165 Limited company (AS) Frosta Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 149,000
Operating profit NOK −37,000
Equity NOK 250,000
Incorporated 2014
Share capital NOK 425,000

Signals

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

REMMAN MASKINDRIFT AS is registered as a limited company in Frosta, Trøndelag with organisation number 913410165. The business is classified under support activities for crop production (NACE 01.610). The company was incorporated in 2014. Registered share capital is NOK 425,000, divided into 850 shares. The company's stated purpose is: “Leie kjøring innen landbruk og industri.”. The most recent filed accounts, for the 2025 financial year, show NOK 149,000 in revenue and NOK −37,000 in operating profit.

Key figures · 2025

Revenue
NOK 149,000
Operating profit
NOK −37,000
Equity
NOK 250,000
Est. value
NOK 202,000

Financial health · 2025

Liquidity
2.22
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
67.6%
Very good
Equity as a share of total capital

Who owns REMMAN MASKINDRIFT AS?

JOHAN PETTER REMMAN
REMMAN MASKINDRIFT AS
NOK 149,000 rev. · NOK −37,000 profit

REMMAN MASKINDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about REMMAN MASKINDRIFT AS

Who owns REMMAN MASKINDRIFT AS?

JOHAN PETTER REMMAN is the largest registered owner, with 50.0%.

What is the revenue of REMMAN MASKINDRIFT AS?

REMMAN MASKINDRIFT AS had revenue of NOK 149,000 in 2025.

Who is the general manager of REMMAN MASKINDRIFT AS?

John-Arve Bratsvedal Remman is registered as general manager of REMMAN MASKINDRIFT AS.

Where is REMMAN MASKINDRIFT AS based?

REMMAN MASKINDRIFT AS has its business address in Frosta.

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.