BIZTRAC BETA
Architectural activities

LY ARKITEKTER AS

Org. no. 984050259 Limited company (AS) Kristiansand Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 12.5m
Operating profit NOK 754,000
Equity NOK 1.5m
Incorporated 2001
Employees 6
Share capital NOK 190,000

LY ARKITEKTER AS is registered as a limited company in Kristiansand, Agder with organisation number 984050259. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2001 and has 6 registered employees. Registered share capital is NOK 190,000, divided into 3800 shares. The company's stated purpose is: “Rådgivning, konsulenttjenester og arkitekttjenester, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.5m in revenue and NOK 754,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.5m
Operating profit
NOK 754,000
Equity
NOK 1.5m
Est. value
NOK 4.5m

Financial health · 2024

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.9%
Good
Equity as a share of total capital

Who owns LY ARKITEKTER AS?

SASEB AS
LY ARKITEKTER AS
NOK 12.5m rev. · NOK 754,000 profit

LY ARKITEKTER AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LY ARKITEKTER AS own?

LY ARKITEKTER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LY ARKITEKTER AS

Who owns LY ARKITEKTER AS?

SASEB AS is the largest registered owner, with 66.0%.

What is the revenue of LY ARKITEKTER AS?

LY ARKITEKTER AS had revenue of NOK 12.5m in 2024.

Who is the general manager of LY ARKITEKTER AS?

Svein Erik Krokmo Bjorvand is registered as general manager of LY ARKITEKTER AS.

Where is LY ARKITEKTER AS based?

LY ARKITEKTER AS has its business address in Kristiansand S.

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.