BIZTRAC BETA
Site preparation

BRØDERUD GRAVESERVICE AS

Org. no. 917808260 Limited company (AS) Kongsvinger Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 27.0m
Operating profit NOK 11.4m
Equity NOK 1.2m
Incorporated 2016
Employees 10
Share capital NOK 1.0m

BRØDERUD GRAVESERVICE AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 917808260. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2016 and has 10 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Anleggsvirksomhet, transport og andre tjenester tilknyttet transport, samt deltakelse i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 27.0m in revenue and NOK 11.4m in operating profit.

Key figures · 2024

Revenue
NOK 27.0m
Operating profit
NOK 11.4m
Equity
NOK 1.2m
Est. value
NOK 31.4m

Financial health · 2024

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

Who owns BRØDERUD GRAVESERVICE AS?

BRØDERUD HOLDING AS
BRØDERUD GRAVESERVICE AS
NOK 27.0m rev. · NOK 11.4m profit

BRØDERUD GRAVESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRØDERUD GRAVESERVICE AS

Who owns BRØDERUD GRAVESERVICE AS?

BRØDERUD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BRØDERUD GRAVESERVICE AS?

BRØDERUD GRAVESERVICE AS had revenue of NOK 27.0m in 2024.

Who is the general manager of BRØDERUD GRAVESERVICE AS?

Stian Aur Brøderud is registered as general manager of BRØDERUD GRAVESERVICE AS.

Where is BRØDERUD GRAVESERVICE AS based?

BRØDERUD GRAVESERVICE AS has its business address in Kongsvinger.

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.