BIZTRAC BETA
Rental and operating of own or leased real estate

FRØYTOR EIENDOM AS

Org. no. 925550019 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 1.3m
Equity NOK 1.2m
Incorporated 2020
Share capital NOK 38,000

Signals

1 flags
  • Nylig endring 2026-03-20 Adresseendring registrert 2026-03-20.

FRØYTOR EIENDOM AS is registered as a limited company in Asker, Akershus with organisation number 925550019. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 38,000, divided into 100 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 1.3m
Equity
NOK 1.2m
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
0.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
43.5%
Very good
Equity as a share of total capital

Who owns FRØYTOR EIENDOM AS?

FRØYTOR HOLDING AS
FRØYTOR EIENDOM AS
NOK 1.7m rev. · NOK 1.3m profit

FRØYTOR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRØYTOR EIENDOM AS

Who owns FRØYTOR EIENDOM AS?

FRØYTOR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FRØYTOR EIENDOM AS?

FRØYTOR EIENDOM AS had revenue of NOK 1.7m in 2024.

Who is the general manager of FRØYTOR EIENDOM AS?

Per Ole Grindvold is registered as general manager of FRØYTOR EIENDOM AS.

Where is FRØYTOR EIENDOM AS based?

FRØYTOR EIENDOM AS has its business address in Billingstad.

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.