BIZTRAC BETA
Public relations and communication activities

PREGE AS

Org. no. 920810594 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK −147,000
Equity NOK 470,000
Incorporated 2018
Employees 6
Share capital NOK 30,000

Signals

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

PREGE AS is registered as a limited company in Drammen, Buskerud with organisation number 920810594. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2018 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Konsulentarbeid og rådgivning innen markedsføring og kommunikasjon, investering i aksjer og andre verdipapirer og alt som står i forbindelse med dette - herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.1m in revenue and NOK −147,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
Operating profit
NOK −147,000
Equity
NOK 470,000
Est. value
NOK 5.6m

Financial health · 2025

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

Who owns PREGE AS?

IDESA AS
PREGE AS
NOK 5.1m rev. · NOK −147,000 profit

PREGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PREGE AS

Who owns PREGE AS?

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

What is the revenue of PREGE AS?

PREGE AS had revenue of NOK 5.1m in 2025.

Who is the general manager of PREGE AS?

Markus Dahlmann Sanden is registered as general manager of PREGE AS.

Where is PREGE AS based?

PREGE AS has its business address in Solbergelva.

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.