BIZTRAC BETA
COMPANY REGISTER PROFILE
930518018 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SWK AS

Org. no. 930518018 Limited company (AS) Strand Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 2,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

SWK AS is registered as a limited company in Strand, Rogaland with organisation number 930518018. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Erverve, eie og forvalte aksjer og andeler i andre selskaper og alt som naturlig hører inn under dette.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −12 %
Equity
NOK 2,000
▼ −84 %
Est. value
NOK 2,000

Financial health · 2025

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.2%
Weak
Equity as a share of total capital

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

Who owns SWK AS?

SWK AS
· NOK −8,000 profit

SWK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SWK AS

Who owns SWK AS?

SIGURD WAAGE KLEPPA is the largest registered owner, with 100.0%.

Where is SWK AS based?

SWK AS has its business address in Jørpeland.

Property

Business address Klovsteinsvegen 17, 4104 Jørpeland
Cadastral unit 1130-47/463/0/0
Building Enebolig · 1 unit

6 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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