BIZTRAC BETA
Wholesale of agricultural machinery, equipment and supplies

FLORUM MASKIN AS

Org. no. 983201539 Limited company (AS) Trondheim Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 18.7m
Operating profit NOK 1.1m
Equity NOK 4.4m
Incorporated 2001
Employees 8
Share capital NOK 100,000

FLORUM MASKIN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 983201539. The business is classified under wholesale of agricultural machinery, equipment and supplies (NACE 46.610). The company was incorporated in 2001 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av maskiner, maskindeler, hageutstyr, jakt- og fritidsklær samt forretningsdrift som naturlig hører sammen med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 18.7m
Operating profit
NOK 1.1m
Equity
NOK 4.4m
Est. value
NOK 6.6m

Financial health · 2024

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

Who owns FLORUM MASKIN AS?

HÅKON RØRSET
FLORUM MASKIN AS
NOK 18.7m rev. · NOK 1.1m profit

FLORUM MASKIN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLORUM MASKIN AS

Who owns FLORUM MASKIN AS?

HÅKON RØRSET is the largest registered owner, with 50.0%.

What is the revenue of FLORUM MASKIN AS?

FLORUM MASKIN AS had revenue of NOK 18.7m in 2024.

Who is the general manager of FLORUM MASKIN AS?

Mikael Tregren Kvittem is registered as general manager of FLORUM MASKIN AS.

Where is FLORUM MASKIN AS based?

FLORUM MASKIN AS has its business address in Trondheim.

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.