BIZTRAC BETA
Cutting, shaping and finishing of stone

TRONDHEIM GRAVMONUMENTER AS

Org. no. 974470144 Limited company (AS) Trondheim Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 18.7m
Operating profit NOK 2.6m
Equity NOK 16.0m
Incorporated 1995
Employees 7
Share capital NOK 100,000

TRONDHEIM GRAVMONUMENTER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 974470144. The business is classified under cutting, shaping and finishing of stone (NACE 23.700). The company was incorporated in 1995 and has 7 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Handel, produksjon og annen økonomisk virksomhet, herunder å delta i norske og utenlandske selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.7m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 18.7m
Operating profit
NOK 2.6m
Equity
NOK 16.0m
Est. value
NOK 14.1m

Financial health · 2024

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

Who owns TRONDHEIM GRAVMONUMENTER AS?

KEN KVISETH
TRONDHEIM GRAVMONUMENTER AS
NOK 18.7m rev. · NOK 2.6m profit

TRONDHEIM GRAVMONUMENTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRONDHEIM GRAVMONUMENTER AS

Who owns TRONDHEIM GRAVMONUMENTER AS?

KEN KVISETH is the largest registered owner, with 50.0%.

What is the revenue of TRONDHEIM GRAVMONUMENTER AS?

TRONDHEIM GRAVMONUMENTER AS had revenue of NOK 18.7m in 2024.

Who is the general manager of TRONDHEIM GRAVMONUMENTER AS?

Kari Gjerde Kviseth is registered as general manager of TRONDHEIM GRAVMONUMENTER AS.

Where is TRONDHEIM GRAVMONUMENTER AS based?

TRONDHEIM GRAVMONUMENTER AS has its business address in Bosberg.

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.