BIZTRAC BETA
COMPANY REGISTER PROFILE
913754433 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

MIGHTY REDS AS

Org. no. 913754433 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −29,000
Equity NOK 1.6m
Incorporated 2014
Share capital NOK 30,000

Signals

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

MIGHTY REDS AS is registered as a limited company in Bergen, Vestland with organisation number 913754433. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper, samt andre tjenester som naturlig faller sammen med dette. Herunder å delta i andre selskapet med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −29,000
Equity
NOK 1.6m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns MIGHTY REDS AS?

SIGBJØRN VELLE
MIGHTY REDS AS
· NOK −29,000 profit

MIGHTY REDS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MIGHTY REDS AS own?

MIGHTY REDS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MIGHTY REDS AS

Who owns MIGHTY REDS AS?

SIGBJØRN VELLE is the largest registered owner, with 100.0%.

Who is the general manager of MIGHTY REDS AS?

Sigbjørn Velle is registered as general manager of MIGHTY REDS AS.

Where is MIGHTY REDS AS based?

MIGHTY REDS AS has its business address in Fyllingsdalen.

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.