biztrac. BETA
COMPANY REGISTER PROFILE
915149421 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

FRUCO AS

Org. no. 915149421 Limited company (AS) Oslo Incorporated 2015 Active
Revenue 2025 NOK 13,000
Operating profit NOK −6,000
Equity NOK 282,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

FRUCO AS is registered as a limited company in Oslo, Oslo with organisation number 915149421. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i andre selskaper, fast eiendom, handel, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 13,000 in revenue and NOK −6,000 in operating profit.

Former names: FN7 ÅRGANG 2015 VI AS

Key figures · 2025

Revenue
NOK 13,000
▲ +4 %
Operating profit
NOK −6,000
▲ +9 %
Equity
NOK 282,000
▲ +0 %
Est. value
NOK 204,000

Financial health · 2025

Liquidity
804.77
Very good
Current assets ÷ current liabilities
Profitability
0.4%
Not satisfactory
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns FRUCO AS?

FRUCO AS
NOK 13,000 rev. · NOK −6,000 profit

FRUCO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRUCO AS

Who owns FRUCO AS?

FRESH GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of FRUCO AS?

FRUCO AS had revenue of NOK 13,000 in 2025.

Who is the general manager of FRUCO AS?

Tom Ragnar Wilhelmsen is registered as general manager of FRUCO AS.

Where is FRUCO AS based?

FRUCO AS has its business address in Oslo.

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

Report a problem

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