BIZTRAC BETA
Manufacture of paper and paperboard

RANHEIM PAPER & BOARD AS

Org. no. 915725015 Limited company (AS) Trondheim Incorporated 1918 Active
Ownership graph ↗
Revenue 2024 NOK 1.0bn
Operating profit NOK 18.0m
Equity NOK 189.8m
Incorporated 1918
Employees 261
Share capital NOK 3.7m

RANHEIM PAPER & BOARD AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915725015. The business is classified under manufacture of paper and paperboard (NACE 17.120). The company was incorporated in 1918 and has 261 registered employees. Registered share capital is NOK 3.7m, divided into 2281082 shares. The company's stated purpose is: “Å drive produksjon og handel samt å delta som aksjeeier eller parthaver i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0bn in revenue and NOK 18.0m in operating profit.

Key figures · 2024

Revenue
NOK 1.0bn
Operating profit
NOK 18.0m
Equity
NOK 189.8m
Est. value
NOK 149.4m

Financial health · 2024

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

Who owns RANHEIM PAPER & BOARD AS?

FUNDERMAX GMBH
RANHEIM PAPER & BOARD AS
NOK 1.0bn rev. · NOK 18.0m profit

RANHEIM PAPER & BOARD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RANHEIM PAPER & BOARD AS

Who owns RANHEIM PAPER & BOARD AS?

FUNDERMAX GMBH is the largest registered owner, with 100.0%.

What is the revenue of RANHEIM PAPER & BOARD AS?

RANHEIM PAPER & BOARD AS had revenue of NOK 1.0bn in 2024.

Who is the general manager of RANHEIM PAPER & BOARD AS?

Alexander Heinrich Klepp is registered as general manager of RANHEIM PAPER & BOARD AS.

Where is RANHEIM PAPER & BOARD AS based?

RANHEIM PAPER & BOARD AS has its business address in Ranheim.

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.