BIZTRAC BETA
Computer consultancy and computer facilities management activities

BARCELO AS

Org. no. 912319466 Limited company (AS) Lillehammer Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 172,000
Operating profit NOK 125,000
Equity NOK 320,000
Incorporated 2013
Share capital NOK 30,000

BARCELO AS is registered as a limited company in Lillehammer, Innlandet with organisation number 912319466. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulenttjenester innen informasjonsteknologi, samt drift og utvikling av egne og andre selskapers digitale løsninger. Investering i aksjer i andre virksomheter og verdipapirer samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 172,000 in revenue and NOK 125,000 in operating profit.

Key figures · 2024

Revenue
NOK 172,000
Operating profit
NOK 125,000
Equity
NOK 320,000
Est. value
NOK 607,000

Financial health · 2024

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

Who owns BARCELO AS?

ARNSTEIN SOLBREKKE
BARCELO AS
NOK 172,000 rev. · NOK 125,000 profit

BARCELO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BARCELO AS own?

BARCELO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BARCELO AS

Who owns BARCELO AS?

ARNSTEIN SOLBREKKE is the largest registered owner, with 100.0%.

What is the revenue of BARCELO AS?

BARCELO AS had revenue of NOK 172,000 in 2024.

Where is BARCELO AS based?

BARCELO AS has its business address in Vingrom.

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.