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

FOLLOHUS AS

Org. no. 971647590 Limited company (AS) Ås Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 472.3m
Operating profit NOK 7.2m
Equity NOK 33.9m
Incorporated 1994
Employees 45
Share capital NOK 200,000

FOLLOHUS AS is registered as a limited company in Ås, Akershus with organisation number 971647590. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1994 and has 45 registered employees. Registered share capital is NOK 200,000, divided into 50 shares. The company's stated purpose is: “Byggevirksomhet, herunder reparasjonsarbeider, erverv av eiendommer og tomter og alt som står i forbindelse med byggevirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 472.3m in revenue and NOK 7.2m in operating profit.

Key figures · 2025

Revenue
NOK 472.3m
▲ +10 %
Operating profit
NOK 7.2m
▼ −43 %
Equity
NOK 33.9m
▲ +2 %
Est. value
NOK 45.9m

Financial health · 2025

Liquidity
1.00
Weak
Current assets ÷ current liabilities
Profitability
7.0%
Satisfactory
Return on total assets
Solidity
22.1%
Good
Equity as a share of total capital

Who owns FOLLOHUS AS?

FOLLOHUS AS
NOK 472.3m rev. · NOK 7.2m profit

FOLLOHUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOLLOHUS AS

Who owns FOLLOHUS AS?

FOLLOHUS GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of FOLLOHUS AS?

FOLLOHUS AS had revenue of NOK 472.3m in 2025.

Who is the general manager of FOLLOHUS AS?

Kristian Haugen Ruud is registered as general manager of FOLLOHUS AS.

Where is FOLLOHUS AS based?

FOLLOHUS AS has its business address in Vinterbro.

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.