BIZTRAC BETA
Wholesale of fruit and vegetables

RE-GRØNT AS

Org. no. 881308932 Limited company (AS) Tønsberg Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 173,000
Equity NOK −70,000
Incorporated 1999
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−70k kr).

RE-GRØNT AS is registered as a limited company in Tønsberg, Vestfold with organisation number 881308932. The business is classified under wholesale of fruit and vegetables (NACE 46.310). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Handel med jordbruksvarer, transportvirksomhet, samt virksomhet som står i forbindelse hermed, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 173,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 173,000
Equity
NOK −70,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-109.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RE-GRØNT AS?

JAN ERIK AABERG
RE-GRØNT AS
NOK 2.9m rev. · NOK 173,000 profit

RE-GRØNT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RE-GRØNT AS

Who owns RE-GRØNT AS?

JAN ERIK AABERG is the largest registered owner, with 100.0%.

What is the revenue of RE-GRØNT AS?

RE-GRØNT AS had revenue of NOK 2.9m in 2024.

Who is the general manager of RE-GRØNT AS?

Jan Erik Aaberg is registered as general manager of RE-GRØNT AS.

Where is RE-GRØNT AS based?

RE-GRØNT AS has its business address in Våle.

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.