BIZTRAC BETA
COMPANY REGISTER PROFILE
947268538 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

FRACOM EIENDOM AS

Org. no. 947268538 Limited company (AS) Karmøy Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 991,000
Operating profit NOK 566,000
Equity NOK 368,000
Incorporated 1988
Share capital NOK 150,000

FRACOM EIENDOM AS is registered as a limited company in Karmøy, Rogaland with organisation number 947268538. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988. Registered share capital is NOK 150,000, divided into 75 shares. The company's stated purpose is: “Eie og drive eiendommer, samt delta i andre selskap med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 991,000 in revenue and NOK 566,000 in operating profit.

Former names: VHG INNREDNINGER A/S

Key figures · 2025

Revenue
NOK 991,000
▲ +16 %
Operating profit
NOK 566,000
▲ +56 %
Equity
NOK 368,000
▲ +147 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
10.7%
Good
Return on total assets
Solidity
7.0%
Weak
Equity as a share of total capital

Who owns FRACOM EIENDOM AS?

FRACOM EIENDOM AS
NOK 991,000 rev. · NOK 566,000 profit

FRACOM EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRACOM EIENDOM AS

Who owns FRACOM EIENDOM AS?

SHABRA AS is the largest registered owner, with 100.0%.

What is the revenue of FRACOM EIENDOM AS?

FRACOM EIENDOM AS had revenue of NOK 991,000 in 2025.

Who is the general manager of FRACOM EIENDOM AS?

Kay Arne Svendsen is registered as general manager of FRACOM EIENDOM AS.

Where is FRACOM EIENDOM AS based?

FRACOM EIENDOM AS has its business address in Karmsund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.