BIZTRAC BETA
Site preparation

LØKEN GRAVESERVICE AS

Org. no. 876568012 Limited company (AS) Nesbyen Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 227,000
Equity NOK 478,000
Incorporated 1996
Share capital NOK 348,000

LØKEN GRAVESERVICE AS is registered as a limited company in Nesbyen, Buskerud with organisation number 876568012. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1996. Registered share capital is NOK 348,000, divided into 348 shares. The company's stated purpose is: “Transport- og maskinentreprenørvirksomhet og handel.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 227,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK 227,000
Equity
NOK 478,000
Est. value
NOK 792,000

Financial health · 2025

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

Who owns LØKEN GRAVESERVICE AS?

ATTICA AS
LØKEN GRAVESERVICE AS
NOK 4.7m rev. · NOK 227,000 profit

LØKEN GRAVESERVICE AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LØKEN GRAVESERVICE AS own?

LØKEN GRAVESERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LØKEN GRAVESERVICE AS

Who owns LØKEN GRAVESERVICE AS?

ATTICA AS is the largest registered owner, with 48.3%.

What is the revenue of LØKEN GRAVESERVICE AS?

LØKEN GRAVESERVICE AS had revenue of NOK 4.7m in 2025.

Who is the general manager of LØKEN GRAVESERVICE AS?

Jan Erik Løken is registered as general manager of LØKEN GRAVESERVICE AS.

Where is LØKEN GRAVESERVICE AS based?

LØKEN GRAVESERVICE AS has its business address in Nesbyen.

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.