biztrac. BETA
COMPANY REGISTER PROFILE
955552237 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

OME FINANS AS

Org. no. 955552237 Limited company (AS) Bjørnafjorden Incorporated 1990 Active
Revenue 2025 NOK 1.2m
Operating profit NOK 716,000
Equity NOK 3.5m
Incorporated 1990
Share capital NOK 100,000

OME FINANS AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 955552237. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1990. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av fast eiendom, handel, kjøp, salg og utleie av nye og brukte transportmidler, deltagelse i andre selskaper og hva dermed er forbundet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 716,000 in operating profit.

Former names: OS MASKINERING EIENDOM AS

Key figures · 2025

Revenue
NOK 1.2m
▲ +33 %
Operating profit
NOK 716,000
▲ +118 %
Equity
NOK 3.5m
▲ +20 %
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
27.90
Very good
Current assets ÷ current liabilities
Profitability
7.2%
Satisfactory
Return on total assets
Solidity
34.9%
Good
Equity as a share of total capital

Who owns OME FINANS AS?

OME FINANS AS
NOK 1.2m rev. · NOK 716,000 profit

OME FINANS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OME FINANS AS

Who owns OME FINANS AS?

ROLFSITT AS is the largest registered owner, with 100.0%.

What is the revenue of OME FINANS AS?

OME FINANS AS had revenue of NOK 1.2m in 2025.

Who is the general manager of OME FINANS AS?

Rolf Haugland is registered as general manager of OME FINANS AS.

Where is OME FINANS AS based?

OME FINANS AS has its business address in Os.

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.