BIZTRAC BETA
Non-specialised wholesale of food, beverages and tobacco

KJEDESERVICE AS

Org. no. 981468635 Limited company (AS) Gjøvik Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 494,000
Incorporated 2000
Share capital NOK 500,000

Signals

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

KJEDESERVICE AS is registered as a limited company in Gjøvik, Innlandet with organisation number 981468635. The business is classified under non-specialised wholesale of food, beverages and tobacco (NACE 46.390). The company was incorporated in 2000. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Handel og agenturvirksomhet og alt hva hermed står i forbindelse, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 494,000
Est. value
NOK 618,000

Financial health · 2024

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

Who owns KJEDESERVICE AS?

ØSTLANDSKE KOLONIALAGENTURER AS
KJEDESERVICE AS
NOK 0 rev. · NOK −3,000 profit

KJEDESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJEDESERVICE AS

Who owns KJEDESERVICE AS?

ØSTLANDSKE KOLONIALAGENTURER AS is the largest registered owner, with 100.0%.

What is the revenue of KJEDESERVICE AS?

KJEDESERVICE AS had revenue of NOK 0 in 2025.

Who is the general manager of KJEDESERVICE AS?

Svein Ove Engevold is registered as general manager of KJEDESERVICE AS.

Where is KJEDESERVICE AS based?

KJEDESERVICE AS has its business address in Gjøvik.

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.