BIZTRAC BETA
COMPANY REGISTER PROFILE
969039214 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Restaurant activities

MAXIM AS

Org. no. 969039214 Limited company (AS) Bergen Incorporated 1994 Active
Ownership graph ↗
Equity NOK −694,000
Incorporated 1994
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−694k kr).

MAXIM AS is registered as a limited company in Bergen, Vestland with organisation number 969039214. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 1994. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, stå for drift av og drive utleie av driftsmidler og fast eiendom, samt å eie aksjer og å delta i andre selskaper med tilsvarende formål.”.

Key figures · 2025

Equity
NOK −694,000
▲ +0 %

Financial health · 2025

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

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

Who owns MAXIM AS?

MAXIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAXIM AS

Who owns MAXIM AS?

MAX INVEST AS is the largest registered owner, with 100.0%.

Where is MAXIM AS based?

MAXIM AS has its business address in Nesttun.

Property

Business address c/o Skudal Revisjon & Rådgivning AS Hardangervegen 21, 5224 Nesttun
Cadastral unit 4601-43/7/0/0
Building Annen kontorbygning · 2 units

38 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.