BIZTRAC BETA
Site preparation

ASKER OG BÆRUM GRAVESERVICE AS

Org. no. 970993282 Limited company (AS) Bærum Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 28.6m
Operating profit NOK 752,000
Equity NOK 979,000
Incorporated 1994
Employees 14
Share capital NOK 100,000

ASKER OG BÆRUM GRAVESERVICE AS is registered as a limited company in Bærum, Akershus with organisation number 970993282. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1994 and has 14 registered employees. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Anleggsvirksomhet, samt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.6m in revenue and NOK 752,000 in operating profit.

Key figures · 2024

Revenue
NOK 28.6m
Operating profit
NOK 752,000
Equity
NOK 979,000
Est. value
NOK 2.7m

Financial health · 2024

Liquidity
1.18
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.1%
Satisfactory
Equity as a share of total capital

Who owns ASKER OG BÆRUM GRAVESERVICE AS?

JAN IVAR KEISERAAS
ASKER OG BÆRUM GRAVESERVICE AS
NOK 28.6m rev. · NOK 752,000 profit

ASKER OG BÆRUM GRAVESERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ASKER OG BÆRUM GRAVESERVICE AS

Who owns ASKER OG BÆRUM GRAVESERVICE AS?

JAN IVAR KEISERAAS is the largest registered owner, with 70.0%.

What is the revenue of ASKER OG BÆRUM GRAVESERVICE AS?

ASKER OG BÆRUM GRAVESERVICE AS had revenue of NOK 28.6m in 2024.

Who is the general manager of ASKER OG BÆRUM GRAVESERVICE AS?

Jan Ivar Keiseraas is registered as general manager of ASKER OG BÆRUM GRAVESERVICE AS.

Where is ASKER OG BÆRUM GRAVESERVICE AS based?

ASKER OG BÆRUM GRAVESERVICE AS has its business address in Skui.

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.