BIZTRAC BETA
Collection of non-hazardous waste

KJETIL JEGLEIM AS

Org. no. 892644012 Limited company (AS) Gol Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 9,000
Operating profit NOK −1.2m
Equity NOK 2.0m
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,2 mill kr).

KJETIL JEGLEIM AS is registered as a limited company in Gol, Buskerud with organisation number 892644012. The business is classified under collection of non-hazardous waste (NACE 38.110). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Renovasjon og avfallshåndtering, herunder utleie og tømming av containere, transport. Deltakelse i andre selskaper med liknende virksomhet ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 9,000 in revenue and NOK −1.2m in operating profit.

Key figures · 2025

Revenue
NOK 9,000
Operating profit
NOK −1.2m
Equity
NOK 2.0m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns KJETIL JEGLEIM AS?

KJETIL JEGLEIM
KJETIL JEGLEIM AS
NOK 9,000 rev. · NOK −1.2m profit

KJETIL JEGLEIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJETIL JEGLEIM AS

Who owns KJETIL JEGLEIM AS?

KJETIL JEGLEIM is the largest registered owner, with 100.0%.

What is the revenue of KJETIL JEGLEIM AS?

KJETIL JEGLEIM AS had revenue of NOK 9,000 in 2025.

Who is the general manager of KJETIL JEGLEIM AS?

Kjetil Jegleim is registered as general manager of KJETIL JEGLEIM AS.

Where is KJETIL JEGLEIM AS based?

KJETIL JEGLEIM AS has its business address in Gol.

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.