biztrac. BETA
COMPANY REGISTER PROFILE
936695094 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

KAMPENESMOSEN LAGER AS

Org. no. 936695094 Limited company (AS) Sarpsborg Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −66,000
Equity NOK 639,000
Incorporated 2025
Share capital NOK 400,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−66k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-09-28 Adresseendring registrert 2026-09-28.

KAMPENESMOSEN LAGER AS is registered as a limited company in Sarpsborg, Østfold with organisation number 936695094. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2025. Registered share capital is NOK 400,000, divided into 1000000 shares. The company's stated purpose is: “Investering og utvikling av eiendom, herunder deltagelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −66,000
Equity
NOK 639,000
Est. value
NOK 583,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
31.4%
Good
Equity as a share of total capital

Who owns KAMPENESMOSEN LAGER AS?

KAMPENESMOSEN LAGER AS
· NOK −66,000 profit

KAMPENESMOSEN LAGER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KAMPENESMOSEN LAGER AS

Who owns KAMPENESMOSEN LAGER AS?

S KARLSEN HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of KAMPENESMOSEN LAGER AS?

Guttorm Frisell is registered as general manager of KAMPENESMOSEN LAGER AS.

Where is KAMPENESMOSEN LAGER AS based?

KAMPENESMOSEN LAGER AS has its business address in Ise.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.