BIZTRAC BETA
Rental and operating of own or leased real estate

PAUL REGGESTAD AS

Org. no. 989962620 Limited company (AS) Holmestrand Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 53,000
Operating profit NOK −288,000
Equity NOK 1.6m
Incorporated 2006
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−288k kr).

PAUL REGGESTAD AS is registered as a limited company in Holmestrand, Vestfold with organisation number 989962620. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Landbruksdrift og eie aksjer i tilsvarende virksomhet, samt annet som naturlig hører inn under dette. ”. The most recent filed accounts, for the 2024 financial year, show NOK 53,000 in revenue and NOK −288,000 in operating profit.

Key figures · 2024

Revenue
NOK 53,000
Operating profit
NOK −288,000
Equity
NOK 1.6m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns PAUL REGGESTAD AS?

PAUL REGGESTAD
PAUL REGGESTAD AS
NOK 53,000 rev. · NOK −288,000 profit

PAUL REGGESTAD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PAUL REGGESTAD AS

Who owns PAUL REGGESTAD AS?

PAUL REGGESTAD is the largest registered owner, with 60.0%.

What is the revenue of PAUL REGGESTAD AS?

PAUL REGGESTAD AS had revenue of NOK 53,000 in 2024.

Who is the general manager of PAUL REGGESTAD AS?

Paul Reggestad is registered as general manager of PAUL REGGESTAD AS.

Where is PAUL REGGESTAD AS based?

PAUL REGGESTAD AS has its business address in Holmestrand.

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.