biztrac. BETA
COMPANY REGISTER PROFILE
931989464 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠NKF SEMINAR AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Organisation of conventions and trade shows

NKF SEMINAR AS

Org. no. 931989464 Limited company (AS) Stavanger Incorporated 2023 In liquidation
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 19,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

NKF SEMINAR AS is registered as a limited company in Stavanger, Rogaland with organisation number 931989464. The business is classified under organisation of conventions and trade shows (NACE 82.300). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Arrangering av møter, samlinger og seminarer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
▲ +24 %
Equity
NOK 19,000
▼ −19 %

Financial health · 2025

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

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

Who owns NKF SEMINAR AS?

NKF SEMINAR AS
NOK 0 rev. · NOK −5,000 profit

NKF SEMINAR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NKF SEMINAR AS

Who owns NKF SEMINAR AS?

NORSK KORROSJONSTEKNISK FORENING AVD. STAVANGER is the largest registered owner, with 100.0%.

What is the revenue of NKF SEMINAR AS?

NKF SEMINAR AS had revenue of NOK 0 in 2025.

Where is NKF SEMINAR AS based?

NKF SEMINAR AS has its business address in Stavanger.

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.