BIZTRAC BETA
Rental and operating of own or leased real estate

KREMTOMTA AS

Org. no. 992779322 Limited company (AS) Kongsvinger Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 2.5m
Equity NOK 2.0m
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KREMTOMTA AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 992779322. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eiendomserverv, eiendomsutvikling og drift, samt alt i forbindelse hermed, herunder å delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 2.5m
Equity
NOK 2.0m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns KREMTOMTA AS?

ØSTERDALSPORTEN AS
KREMTOMTA AS
NOK 3.7m rev. · NOK 2.5m profit

KREMTOMTA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KREMTOMTA AS

Who owns KREMTOMTA AS?

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

What is the revenue of KREMTOMTA AS?

KREMTOMTA AS had revenue of NOK 3.7m in 2024.

Who is the general manager of KREMTOMTA AS?

Karl Erik Rimfeldt is registered as general manager of KREMTOMTA AS.

Where is KREMTOMTA AS based?

KREMTOMTA AS has its business address in Kongsvinger.

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.