BIZTRAC BETA
Manufacture of other general-purpose machinery n.e.c.

FRODE WAAGAN AS

Org. no. 931357484 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 86,000
Operating profit NOK −112,000
Equity NOK 157,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

FRODE WAAGAN AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 931357484. The business is classified under manufacture of other general-purpose machinery n.e.c. (NACE 28.290). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produksjon, konstruksjon, montering og service til næringsmiddelindustrien, samt det som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 86,000 in revenue and NOK −112,000 in operating profit.

Key figures · 2025

Revenue
NOK 86,000
Operating profit
NOK −112,000
Equity
NOK 157,000
Est. value
NOK 129,000

Financial health · 2025

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

Who owns FRODE WAAGAN AS?

FRODE WAAGAN
FRODE WAAGAN AS
NOK 86,000 rev. · NOK −112,000 profit

FRODE WAAGAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRODE WAAGAN AS

Who owns FRODE WAAGAN AS?

FRODE WAAGAN is the largest registered owner, with 100.0%.

What is the revenue of FRODE WAAGAN AS?

FRODE WAAGAN AS had revenue of NOK 86,000 in 2025.

Who is the general manager of FRODE WAAGAN AS?

Frode Waagan is registered as general manager of FRODE WAAGAN AS.

Where is FRODE WAAGAN AS based?

FRODE WAAGAN AS has its business address in Skodje.

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.