BIZTRAC BETA
Other building and industrial cleaning activities

IBY AS

Org. no. 961668557 Limited company (AS) Lier Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −260,000
Equity NOK 1.4m
Incorporated 1991
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−260k kr).

IBY AS is registered as a limited company in Lier, Buskerud with organisation number 961668557. The business is classified under other building and industrial cleaning activities (NACE 81.220). The company was incorporated in 1991. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Salg av konsulenttjenester, kjøp og utleie av driftsmidler, samt investering i eiendommer, aksjer og verdipapirer.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −260,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −260,000
Equity
NOK 1.4m
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.6%
Satisfactory
Equity as a share of total capital

Who owns IBY AS?

YNGVE KRISTIANSEN BERTHINUSSEN
IBY AS
NOK 1.5m rev. · NOK −260,000 profit

IBY AS has 4 registered shareholders:

All shareholders and roles →

Which companies does IBY AS own?

IBY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about IBY AS

Who owns IBY AS?

YNGVE KRISTIANSEN BERTHINUSSEN is the largest registered owner, with 31.7%.

What is the revenue of IBY AS?

IBY AS had revenue of NOK 1.5m in 2024.

Who is the general manager of IBY AS?

Bjørn Inge Berthinussen is registered as general manager of IBY AS.

Where is IBY AS based?

IBY AS has its business address in Lier.

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.