BIZTRAC BETA
Site preparation

FRANK WAAGEN TRANSPORT AS

Org. no. 913492552 Limited company (AS) Øygarden Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 232,000
Operating profit NOK −25,000
Equity NOK 25,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

FRANK WAAGEN TRANSPORT AS is registered as a limited company in Øygarden, Vestland with organisation number 913492552. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreprenør innenfor bygg og anlegg, utleie av utstyr, transport, kjøp -og salg av eiendom og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 232,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 232,000
Operating profit
NOK −25,000
Equity
NOK 25,000
Est. value
NOK 160,000

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.9%
Weak
Equity as a share of total capital

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

Who owns FRANK WAAGEN TRANSPORT AS?

FRANK WAAGEN
FRANK WAAGEN TRANSPORT AS
NOK 232,000 rev. · NOK −25,000 profit

FRANK WAAGEN TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRANK WAAGEN TRANSPORT AS

Who owns FRANK WAAGEN TRANSPORT AS?

FRANK WAAGEN is the largest registered owner, with 100.0%.

What is the revenue of FRANK WAAGEN TRANSPORT AS?

FRANK WAAGEN TRANSPORT AS had revenue of NOK 232,000 in 2025.

Where is FRANK WAAGEN TRANSPORT AS based?

FRANK WAAGEN TRANSPORT AS has its business address in Straume.

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.