BIZTRAC BETA
Retail sale of watches and jewellery

P.F. WAAGE A/S

Org. no. 945946318 Limited company (AS) Ulstein Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 92,000
Equity NOK 3.3m
Incorporated 1987
Employees 8
Share capital NOK 693,000

P.F. WAAGE A/S is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 945946318. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 1987 and has 8 registered employees. Registered share capital is NOK 693,000, divided into 198 shares. The company's stated purpose is: “Selskapets formål er å drive handel, fortrinnsvis med gullsmedvarer, glass og stentøy, portefølje- artikler, parfyme og ellers andre varer som hermed står i forbindelse, samt å delta i andre foretak med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 92,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 92,000
Equity
NOK 3.3m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns P.F. WAAGE A/S?

ARILD WAAGE
P.F. WAAGE A/S
NOK 5.3m rev. · NOK 92,000 profit

P.F. WAAGE A/S has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about P.F. WAAGE A/S

Who owns P.F. WAAGE A/S?

ARILD WAAGE is the largest registered owner, with 100.0%.

What is the revenue of P.F. WAAGE A/S?

P.F. WAAGE A/S had revenue of NOK 5.3m in 2025.

Who is the general manager of P.F. WAAGE A/S?

Arild Waage is registered as general manager of P.F. WAAGE A/S.

Where is P.F. WAAGE A/S based?

P.F. WAAGE A/S has its business address in Ulsteinvik.

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.