BIZTRAC BETA
Other captive investment companies

FRODE MASTAD HOLDING AS

Org. no. 989124412 Limited company (AS) Melhus Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −23,000
Equity NOK 86,000
Incorporated 2005
Share capital NOK 456,000

Signals

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

FRODE MASTAD HOLDING AS is registered as a limited company in Melhus, Trøndelag with organisation number 989124412. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 456,000, divided into 456 shares. The company's stated purpose is: “Selskapets formål er å drive med aksjeinvesteringer, samt hva dermed står i forbindelse med, herunder å delta i andre selskaper med lignende virksomhet. ”.

Key figures · 2025

Operating profit
NOK −23,000
Equity
NOK 86,000
Est. value
NOK 79,000

Financial health · 2025

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.8%
Weak
Equity as a share of total capital

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

Who owns FRODE MASTAD HOLDING AS?

FRODE MASTAD
FRODE MASTAD HOLDING AS
· NOK −23,000 profit

FRODE MASTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRODE MASTAD HOLDING AS own?

FRODE MASTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FRODE MASTAD HOLDING AS

Who owns FRODE MASTAD HOLDING AS?

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

Who is the general manager of FRODE MASTAD HOLDING AS?

Frode Mastad is registered as general manager of FRODE MASTAD HOLDING AS.

Where is FRODE MASTAD HOLDING AS based?

FRODE MASTAD HOLDING AS has its business address in Melhus.

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.