biztrac. BETA
COMPANY REGISTER PROFILE
821209412 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KNUSK AS

Org. no. 821209412 Limited company (AS) Haugesund Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 252,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

KNUSK AS is registered as a limited company in Haugesund, Rogaland with organisation number 821209412. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av verdipapirer og eiendom, utleie av eiendom, utlån av penger, rådgivning, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
▼ −244 %
Equity
NOK 252,000
▼ −2 %
Est. value
NOK 230,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-1.5%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns KNUSK AS?

KNUSK AS
NOK 0 rev. · NOK −4,000 profit

KNUSK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KNUSK AS own?

KNUSK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KNUSK AS

Who owns KNUSK AS?

Ørjan Svendsen is the largest registered owner, with 100.0%.

What is the revenue of KNUSK AS?

KNUSK AS had revenue of NOK 0 in 2025.

Where is KNUSK AS based?

KNUSK AS has its business address in Haugesund.

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.