biztrac. BETA
COMPANY REGISTER PROFILE
993533556 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

BLAS AS

Org. no. 993533556 Limited company (AS) Klepp Incorporated 2009 Active
Operating profit NOK −4,000
Equity NOK −1.6m
Incorporated 2009
Share capital NOK 159,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,6 mill kr).

BLAS AS is registered as a limited company in Klepp, Rogaland with organisation number 993533556. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2009. Registered share capital is NOK 159,000, divided into 1592 shares. The company's stated purpose is: “Bedriftsrådgivning og annen administrativ rådgivning, samt å kunne utføre tjenester i denne forbindelsen. Selskapet skal også kunne eie andeler eller aksjer i andre selskaper, investere i fast eiendom, samt alt som står i forbindelse med dette.”.

Former names: UELAND INVEST AS

Key figures · 2025

Operating profit
NOK −4,000
▲ +4 %
Equity
NOK −1.6m
▼ −0 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
-6.7%
Not satisfactory
Return on total assets
Solidity
-2737.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BLAS AS?

BLAS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BLAS AS own?

BLAS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BLAS AS

Who owns BLAS AS?

Lars Arne Ueland is the largest registered owner, with 50.0%.

Who is the general manager of BLAS AS?

Svein Børge Ueland is registered as general manager of BLAS AS.

Where is BLAS AS based?

BLAS AS has its business address in Orre.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.