BIZTRAC BETA
Restaurant activities

BYLIV AS

Org. no. 832059102 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 998,000
Operating profit NOK −2.2m
Equity NOK 13.1m
Incorporated 2023
Share capital NOK 162,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,2 mill kr).
  • Nylig endring 2026-06-30 Adresseendring registrert 2026-06-30.

BYLIV AS is registered as a limited company in Oslo, Oslo with organisation number 832059102. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023. Registered share capital is NOK 162,000, divided into 1624740 shares. The company's stated purpose is: “Investeringer i aksjer og andre eierandeler i andre selskaper og foretak, samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 998,000 in revenue and NOK −2.2m in operating profit.

Key figures · 2024

Revenue
NOK 998,000
Operating profit
NOK −2.2m
Equity
NOK 13.1m
Est. value
NOK 7.3m

Financial health · 2024

Liquidity
10.28
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
90.8%
Very good
Equity as a share of total capital

Who owns BYLIV AS?

LIGNAGE AS
BYLIV AS
NOK 998,000 rev. · NOK −2.2m profit

BYLIV AS has 18 registered shareholders:

All shareholders and roles →

Which companies does BYLIV AS own?

BYLIV AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about BYLIV AS

Who owns BYLIV AS?

LIGNAGE AS is the largest registered owner, with 14.4%.

What is the revenue of BYLIV AS?

BYLIV AS had revenue of NOK 998,000 in 2024.

Who is the general manager of BYLIV AS?

Jørgen Stråtveit is registered as general manager of BYLIV AS.

Where is BYLIV AS based?

BYLIV AS has its business address in Oslo.

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.