BIZTRAC BETA
Construction of residential and non-residential buildings

BARMEN BYGG AS

Org. no. 998595762 Limited company (AS) Risør Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK 561,000
Equity NOK 2.7m
Incorporated 2012
Share capital NOK 40,000

BARMEN BYGG AS is registered as a limited company in Risør, Agder with organisation number 998595762. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Bygg- og tømrervirksomhet. Samt eie og forvalte akjser og annet som naturlig tilhører området.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK 561,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
Operating profit
NOK 561,000
Equity
NOK 2.7m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns BARMEN BYGG AS?

TORMOD BARMEN STRAND
BARMEN BYGG AS
NOK 5.6m rev. · NOK 561,000 profit

BARMEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BARMEN BYGG AS own?

BARMEN BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BARMEN BYGG AS

Who owns BARMEN BYGG AS?

TORMOD BARMEN STRAND is the largest registered owner, with 100.0%.

What is the revenue of BARMEN BYGG AS?

BARMEN BYGG AS had revenue of NOK 5.6m in 2025.

Who is the general manager of BARMEN BYGG AS?

Tormod Barmen Strand is registered as general manager of BARMEN BYGG AS.

Where is BARMEN BYGG AS based?

BARMEN BYGG AS has its business address in Risør.

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.