BIZTRAC BETA
Wholesale of fruit and vegetables

NORFRESH SERVICEPARTNER AS

Org. no. 992744405 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 23.6m
Operating profit NOK 270,000
Equity NOK 1.5m
Incorporated 2008
Employees 6
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NORFRESH SERVICEPARTNER AS is registered as a limited company in Oslo, Oslo with organisation number 992744405. The business is classified under wholesale of fruit and vegetables (NACE 46.310). The company was incorporated in 2008 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Engroshandel med frukt og grønnsaker, samt investering og deltakelse i andre selskaper og virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 23.6m in revenue and NOK 270,000 in operating profit.

Key figures · 2024

Revenue
NOK 23.6m
Operating profit
NOK 270,000
Equity
NOK 1.5m
Est. value
NOK 1.8m

Financial health · 2024

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.7%
Good
Equity as a share of total capital

Who owns NORFRESH SERVICEPARTNER AS?

NORFRESH AS
NORFRESH SERVICEPARTNER AS
NOK 23.6m rev. · NOK 270,000 profit

NORFRESH SERVICEPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORFRESH SERVICEPARTNER AS

Who owns NORFRESH SERVICEPARTNER AS?

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

What is the revenue of NORFRESH SERVICEPARTNER AS?

NORFRESH SERVICEPARTNER AS had revenue of NOK 23.6m in 2024.

Where is NORFRESH SERVICEPARTNER AS based?

NORFRESH SERVICEPARTNER 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 15.06.2026.

Report a problem

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