BIZTRAC BETA
COMPANY REGISTER PROFILE
989035487 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

ØRJAN INVEST AS

Org. no. 989035487 Limited company (AS) Kvinnherad Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −58,000
Equity NOK 1.8m
Incorporated 2005
Share capital NOK 162,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−58k kr).

ØRJAN INVEST AS is registered as a limited company in Kvinnherad, Vestland with organisation number 989035487. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 162,000, divided into 1800 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, forvalte eierinteressene av disse samt eie, drive utleie av og utvikle fast eiendom. Selskapet skal også kunne forestå administrative tjenester for andre selskaper.”.

Key figures · 2025

Operating profit
NOK −58,000
▼ −563 %
Equity
NOK 1.8m
▼ −41 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.8%
Not satisfactory
Return on total assets
Solidity
25.6%
Good
Equity as a share of total capital

Who owns ØRJAN INVEST AS?

ØRJAN INVEST AS
· NOK −58,000 profit

ØRJAN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØRJAN INVEST AS own?

ØRJAN INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ØRJAN INVEST AS

Who owns ØRJAN INVEST AS?

ØRJAN TEIGEN is the largest registered owner, with 100.0%.

Who is the general manager of ØRJAN INVEST AS?

Ørjan Teigen is registered as general manager of ØRJAN INVEST AS.

Where is ØRJAN INVEST AS based?

ØRJAN INVEST AS has its business address in Husnes.

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

Report a problem

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