BIZTRAC BETA
Rental and operating of own or leased real estate

GIMEL AS

Org. no. 889175702 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 277,000
Operating profit NOK −1.4m
Equity NOK −734,000
Incorporated 2005
Share capital NOK 255,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−734k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).

GIMEL AS is registered as a limited company in Kristiansand, Agder with organisation number 889175702. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 255,000, divided into 2554 shares. The company's stated purpose is: “Investering i andre selskaper, konsulenttjenester og annen økonomisk virksomhet som naturlig ligger inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 277,000 in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 277,000
Operating profit
NOK −1.4m
Equity
NOK −734,000

Financial health · 2024

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

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

Who owns GIMEL AS?

BJARNE HOVE
GIMEL AS
NOK 277,000 rev. · NOK −1.4m profit

GIMEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GIMEL AS

Who owns GIMEL AS?

BJARNE HOVE is the largest registered owner, with 100.0%.

What is the revenue of GIMEL AS?

GIMEL AS had revenue of NOK 277,000 in 2024.

Who is the general manager of GIMEL AS?

Bjarne Hove is registered as general manager of GIMEL AS.

Where is GIMEL AS based?

GIMEL AS has its business address in Søgne.

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.