BIZTRAC BETA
Retail sale of clothing

HERREAVDELINGEN AS

Org. no. 881424932 Limited company (AS) Modum Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 8.0m
Operating profit NOK 487,000
Equity NOK 2.9m
Incorporated 2000
Employees 6
Share capital NOK 200,000

HERREAVDELINGEN AS is registered as a limited company in Modum, Buskerud with organisation number 881424932. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2000 and has 6 registered employees. Registered share capital is NOK 200,000, divided into 20 shares. The company's stated purpose is: “Handel med klær, eie aksjer/andeler i andre selskaper, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.0m in revenue and NOK 487,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.0m
Operating profit
NOK 487,000
Equity
NOK 2.9m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns HERREAVDELINGEN AS?

RUNAR FLATTUM WAM
HERREAVDELINGEN AS
NOK 8.0m rev. · NOK 487,000 profit

HERREAVDELINGEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HERREAVDELINGEN AS own?

HERREAVDELINGEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HERREAVDELINGEN AS

Who owns HERREAVDELINGEN AS?

RUNAR FLATTUM WAM is the largest registered owner, with 50.0%.

What is the revenue of HERREAVDELINGEN AS?

HERREAVDELINGEN AS had revenue of NOK 8.0m in 2025.

Who is the general manager of HERREAVDELINGEN AS?

Dag Frode Lobben is registered as general manager of HERREAVDELINGEN AS.

Where is HERREAVDELINGEN AS based?

HERREAVDELINGEN AS has its business address in Åmot.

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.