BIZTRAC BETA
Other captive investment companies

MELVIN AS

Org. no. 916838522 Limited company (AS) Kristiansand Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 18,000
Operating profit NOK −10,000
Equity NOK 2.1m
Incorporated 2016
Share capital NOK 34,000

Signals

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

MELVIN AS is registered as a limited company in Kristiansand, Agder with organisation number 916838522. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 34,000, divided into 340 shares. The company's stated purpose is: “Levere konsulenttjenester og andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 18,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 18,000
Operating profit
NOK −10,000
Equity
NOK 2.1m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns MELVIN AS?

FREDRIK MELBY
MELVIN AS
NOK 18,000 rev. · NOK −10,000 profit

MELVIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MELVIN AS own?

MELVIN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MELVIN AS

Who owns MELVIN AS?

FREDRIK MELBY is the largest registered owner, with 100.0%.

What is the revenue of MELVIN AS?

MELVIN AS had revenue of NOK 18,000 in 2025.

Where is MELVIN AS based?

MELVIN AS has its business address in Hamresanden.

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.