biztrac. BETA
COMPANY REGISTER PROFILE
925924709 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

KØRT AS

Org. no. 925924709 Limited company (AS) Modum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 430,000
Operating profit NOK 179,000
Equity NOK −103,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−103k kr).

KØRT AS is registered as a limited company in Modum, Buskerud with organisation number 925924709. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av moteartikler.”. The most recent filed accounts, for the 2025 financial year, show NOK 430,000 in revenue and NOK 179,000 in operating profit.

Key figures · 2025

Revenue
NOK 430,000
Operating profit
NOK 179,000
▲ +171 %
Equity
NOK −103,000
▲ +81 %
Est. value
NOK 304,000

Financial health · 2025

Liquidity
0.19
Not satisfactory
Current assets ÷ current liabilities
Profitability
25.5%
Very good
Return on total assets
Solidity
-12.4%
Weak
Equity as a share of total capital

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

Who owns KØRT AS?

KØRT AS
NOK 430,000 rev. · NOK 179,000 profit

KØRT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KØRT AS own?

KØRT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KØRT AS

Who owns KØRT AS?

Courtney Samantha Marles is the largest registered owner, with 100.0%.

What is the revenue of KØRT AS?

KØRT AS had revenue of NOK 430,000 in 2025.

Who is the general manager of KØRT AS?

Courtney Samantha Marles is registered as general manager of KØRT AS.

Where is KØRT AS based?

KØRT AS has its business address in Åmot.

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.