biztrac. BETA
COMPANY REGISTER PROFILE
946874221 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

S FARMENS MESTERBYGG AS

Org. no. 946874221 Limited company (AS) Hamar Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 52.5m
Operating profit NOK 3.0m
Equity NOK 2.6m
Incorporated 1988
Employees 20
Share capital NOK 100,000

S FARMENS MESTERBYGG AS is registered as a limited company in Hamar, Innlandet with organisation number 946874221. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1988 and has 20 registered employees. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Byggevirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 52.5m in revenue and NOK 3.0m in operating profit.

Key figures · 2025

Revenue
NOK 52.5m
▲ +16 %
Operating profit
NOK 3.0m
▼ −26 %
Equity
NOK 2.6m
▲ +31 %
Est. value
NOK 11.9m

Financial health · 2025

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
18.5%
Very good
Return on total assets
Solidity
13.1%
Satisfactory
Equity as a share of total capital

Who owns S FARMENS MESTERBYGG AS?

S FARMENS MESTERBYGG AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about S FARMENS MESTERBYGG AS

Who owns S FARMENS MESTERBYGG AS?

S. F. INVEST AS is the largest registered owner, with 59.0%.

What is the revenue of S FARMENS MESTERBYGG AS?

S FARMENS MESTERBYGG AS had revenue of NOK 52.5m in 2025.

Who is the general manager of S FARMENS MESTERBYGG AS?

Kent Roar Farmen is registered as general manager of S FARMENS MESTERBYGG AS.

Where is S FARMENS MESTERBYGG AS based?

S FARMENS MESTERBYGG AS has its business address in Ridabu.

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.