BIZTRAC BETA
Rental and operating of own or leased real estate

SIMFRO HOLDING AS

Org. no. 989984527 Limited company (AS) Fredrikstad Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 2.0m
Equity NOK 2.1m
Incorporated 2006
Share capital NOK 100,000

SIMFRO HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 989984527. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, kjøp og salg av verdipapirer, deltakelse i andre selskap, eiendomsutvikling samt øvrig handel og tjenester. ”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 2.0m
Equity
NOK 2.1m
Est. value
NOK 4.5m

Financial health · 2024

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

Who owns SIMFRO HOLDING AS?

TERJE FROST
SIMFRO HOLDING AS
NOK 2.7m rev. · NOK 2.0m profit

SIMFRO HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SIMFRO HOLDING AS own?

SIMFRO HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

SIMFRO HOLDING AS er morselskap for 4 datterselskaper:

Frequently asked questions about SIMFRO HOLDING AS

Who owns SIMFRO HOLDING AS?

TERJE FROST is the largest registered owner, with 50.0%.

What is the revenue of SIMFRO HOLDING AS?

SIMFRO HOLDING AS had revenue of NOK 2.7m in 2024.

Where is SIMFRO HOLDING AS based?

SIMFRO HOLDING AS has its business address in Kråkerøy.

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.