BIZTRAC BETA
Freight transport by road

KVEITEJEGEREN AS

Org. no. 920508383 Limited company (AS) Lillehammer Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 7,000
Operating profit NOK −60,000
Equity NOK −60,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−60k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−60k kr).

KVEITEJEGEREN AS is registered as a limited company in Lillehammer, Innlandet with organisation number 920508383. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Konsulenttjenester, undervisning og matlaging type kokk, restaurant og take-away, renovasjon, sjåførtjenester og det som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7,000 in revenue and NOK −60,000 in operating profit.

Key figures · 2024

Revenue
NOK 7,000
Operating profit
NOK −60,000
Equity
NOK −60,000

Financial health · 2024

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

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

Who owns KVEITEJEGEREN AS?

THOMAS JOSEPH MEISFJORD
KVEITEJEGEREN AS
NOK 7,000 rev. · NOK −60,000 profit

KVEITEJEGEREN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVEITEJEGEREN AS

Who owns KVEITEJEGEREN AS?

THOMAS JOSEPH MEISFJORD is the largest registered owner, with 75.0%.

What is the revenue of KVEITEJEGEREN AS?

KVEITEJEGEREN AS had revenue of NOK 7,000 in 2024.

Where is KVEITEJEGEREN AS based?

KVEITEJEGEREN AS has its business address in Lillehammer.

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.