biztrac. BETA
COMPANY REGISTER PROFILE
935048745 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Intermediation service activities for real estate activities

OMMUNDSEN & BIRKELAND AS

Org. no. 935048745 Limited company (AS) Klepp Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 4.2m
Operating profit NOK 384,000
Equity NOK 590,000
Incorporated 2025
Share capital NOK 125,000

OMMUNDSEN & BIRKELAND AS is registered as a limited company in Klepp, Rogaland with organisation number 935048745. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2025. Registered share capital is NOK 125,000, divided into 10000 shares. The company's stated purpose is: “Drive eiendomsmegling i eget navn og dertil knyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK 384,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
Operating profit
NOK 384,000
Equity
NOK 590,000
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
1.77
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
43.4%
Very good
Equity as a share of total capital

Who owns OMMUNDSEN & BIRKELAND AS?

OMMUNDSEN & BIRKELAND AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about OMMUNDSEN & BIRKELAND AS

Who owns OMMUNDSEN & BIRKELAND AS?

Ann Helen Lauvskar Ommundsen is the largest registered owner, with 40.0%.

What is the revenue of OMMUNDSEN & BIRKELAND AS?

OMMUNDSEN & BIRKELAND AS had revenue of NOK 4.2m in 2025.

Who is the general manager of OMMUNDSEN & BIRKELAND AS?

Ann Helen Lauvskar Ommundsen is registered as general manager of OMMUNDSEN & BIRKELAND AS.

Where is OMMUNDSEN & BIRKELAND AS based?

OMMUNDSEN & BIRKELAND AS has its business address in Kleppe.

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.