BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

G KLØVE LL

Org. no. 913453727 Limited company (AS) Voss Incorporated 1934 Active
Ownership graph ↗
Revenue 2025 NOK 6.8m
Operating profit NOK −279,000
Equity NOK 168,000
Incorporated 1934
Employees 6
Share capital NOK 100,000

Signals

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

G KLØVE LL is registered as a limited company in Voss, Vestland with organisation number 913453727. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1934 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Handel med manufatur, kioskvarer og kva som står i samband med dette, samt å investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.8m in revenue and NOK −279,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.8m
Operating profit
NOK −279,000
Equity
NOK 168,000
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns G KLØVE LL?

GUNNAR KLØVE LILLETHUN
G KLØVE LL
NOK 6.8m rev. · NOK −279,000 profit

G KLØVE LL has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about G KLØVE LL

Who owns G KLØVE LL?

GUNNAR KLØVE LILLETHUN is the largest registered owner, with 48.0%.

What is the revenue of G KLØVE LL?

G KLØVE LL had revenue of NOK 6.8m in 2025.

Who is the general manager of G KLØVE LL?

Brit Anita Solheim is registered as general manager of G KLØVE LL.

Where is G KLØVE LL based?

G KLØVE LL has its business address in Voss.

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.