BIZTRAC BETA
Construction of water projects

BIRKEN & CO AS

Org. no. 988251437 Limited company (AS) Sandnes Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 95.3m
Operating profit NOK 2.0m
Equity NOK 53.7m
Incorporated 2005
Employees 12
Share capital NOK 500,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BIRKEN & CO AS is registered as a limited company in Sandnes, Rogaland with organisation number 988251437. The business is classified under construction of water projects (NACE 42.910). The company was incorporated in 2005 and has 12 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Rådgivning, entreprenørvirksomhet samt deltakelse i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 95.3m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 95.3m
Operating profit
NOK 2.0m
Equity
NOK 53.7m
Est. value
NOK 37.3m

Financial health · 2024

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

Who owns BIRKEN & CO AS?

PER IVAR BIRKELAND AS
BIRKEN & CO AS
NOK 95.3m rev. · NOK 2.0m profit

BIRKEN & CO AS has 5 registered shareholders:

All shareholders and roles →

Which companies does BIRKEN & CO AS own?

BIRKEN & CO AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BIRKEN & CO AS

Who owns BIRKEN & CO AS?

PER IVAR BIRKELAND AS is the largest registered owner, with 25.0%.

What is the revenue of BIRKEN & CO AS?

BIRKEN & CO AS had revenue of NOK 95.3m in 2024.

Where is BIRKEN & CO AS based?

BIRKEN & CO AS has its business address in Sandnes.

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.