BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

LYS BEMANNING AS

Org. no. 923748830 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 25.3m
Operating profit NOK 1.1m
Equity NOK 1.0m
Incorporated 2019
Employees 130
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-23 Adresseendring registrert 2026-06-23.

LYS BEMANNING AS is registered as a limited company in Bergen, Vestland with organisation number 923748830. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2019 and has 130 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie av arbeidskraft.”. The most recent filed accounts, for the 2024 financial year, show NOK 25.3m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 25.3m
Operating profit
NOK 1.1m
Equity
NOK 1.0m
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns LYS BEMANNING AS?

ØYSTEIN LONA SVENDSEN
LYS BEMANNING AS
NOK 25.3m rev. · NOK 1.1m profit

LYS BEMANNING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYS BEMANNING AS

Who owns LYS BEMANNING AS?

ØYSTEIN LONA SVENDSEN is the largest registered owner, with 50.3%.

What is the revenue of LYS BEMANNING AS?

LYS BEMANNING AS had revenue of NOK 25.3m in 2024.

Who is the general manager of LYS BEMANNING AS?

Øystein Lona Svendsen is registered as general manager of LYS BEMANNING AS.

Where is LYS BEMANNING AS based?

LYS BEMANNING AS has its business address in Bergen.

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.