BIZTRAC BETA
Retail sale of motor vehicles

BENESTVEDT EIENDOM AS

Org. no. 989260553 Limited company (AS) Grimstad Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 1.1m
Equity NOK 5.6m
Incorporated 2005
Share capital NOK 100,000

BENESTVEDT EIENDOM AS is registered as a limited company in Grimstad, Agder with organisation number 989260553. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og eiendommer samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 1.1m
Equity
NOK 5.6m
Est. value
NOK 5.4m

Financial health · 2024

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

Who owns BENESTVEDT EIENDOM AS?

PER IVAR BENESTVEDT
BENESTVEDT EIENDOM AS
NOK 1.7m rev. · NOK 1.1m profit

BENESTVEDT EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BENESTVEDT EIENDOM AS own?

BENESTVEDT EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BENESTVEDT EIENDOM AS

Who owns BENESTVEDT EIENDOM AS?

PER IVAR BENESTVEDT is the largest registered owner, with 34.0%.

What is the revenue of BENESTVEDT EIENDOM AS?

BENESTVEDT EIENDOM AS had revenue of NOK 1.7m in 2024.

Who is the general manager of BENESTVEDT EIENDOM AS?

Per Ivar Benestvedt is registered as general manager of BENESTVEDT EIENDOM AS.

Where is BENESTVEDT EIENDOM AS based?

BENESTVEDT EIENDOM AS has its business address in Grimstad.

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.