BIZTRAC BETA
Architectural activities

JK.ARKITEKTUR AS

Org. no. 988287644 Limited company (AS) Stord Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 8.1m
Operating profit NOK 1.9m
Equity NOK 3.4m
Incorporated 2005
Employees 5
Share capital NOK 100,000

JK.ARKITEKTUR AS is registered as a limited company in Stord, Vestland with organisation number 988287644. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2005 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Arkitekturprosjektering planlegging, ideutvikling tilhørende dette fagområdet, investering i andre selskap og hva som naturlig hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.1m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 8.1m
Operating profit
NOK 1.9m
Equity
NOK 3.4m
Est. value
NOK 8.3m

Financial health · 2024

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.8%
Good
Equity as a share of total capital

Who owns JK.ARKITEKTUR AS?

JO KJETIL NIELSEN
JK.ARKITEKTUR AS
NOK 8.1m rev. · NOK 1.9m profit

JK.ARKITEKTUR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JK.ARKITEKTUR AS own?

JK.ARKITEKTUR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JK.ARKITEKTUR AS

Who owns JK.ARKITEKTUR AS?

JO KJETIL NIELSEN is the largest registered owner, with 50.0%.

What is the revenue of JK.ARKITEKTUR AS?

JK.ARKITEKTUR AS had revenue of NOK 8.1m in 2024.

Who is the general manager of JK.ARKITEKTUR AS?

Jo Kjetil Nielsen is registered as general manager of JK.ARKITEKTUR AS.

Where is JK.ARKITEKTUR AS based?

JK.ARKITEKTUR AS has its business address in Stord.

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.