BIZTRAC BETA
Wholesale of fruit and vegetables

Jørgen Sørensen & Co. A/S

Org. no. 945748575 Limited company (AS) Oslo Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK 1.8m
Incorporated 1987
Share capital NOK 1.0m

Signals

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

Jørgen Sørensen & Co. A/S is registered as a limited company in Oslo, Oslo with organisation number 945748575. The business is classified under wholesale of fruit and vegetables (NACE 46.310). The company was incorporated in 1987. Registered share capital is NOK 1.0m, divided into 1030 shares. The company's stated purpose is: “Handelsvirksomhet, kjøp/salg av verdipapirer samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK 1.8m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns Jørgen Sørensen & Co. A/S?

REIDAR SØRENSEN
Jørgen Sørensen & Co. A/S
NOK 0 rev. · NOK −26,000 profit

Jørgen Sørensen & Co. A/S has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about Jørgen Sørensen & Co. A/S

Who owns Jørgen Sørensen & Co. A/S?

REIDAR SØRENSEN is the largest registered owner, with 100.0%.

What is the revenue of Jørgen Sørensen & Co. A/S?

Jørgen Sørensen & Co. A/S had revenue of NOK 0 in 2025.

Who is the general manager of Jørgen Sørensen & Co. A/S?

Reidar Sørensen is registered as general manager of Jørgen Sørensen & Co. A/S.

Where is Jørgen Sørensen & Co. A/S based?

Jørgen Sørensen & Co. A/S 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.