biztrac. BETA
COMPANY REGISTER PROFILE
911825716 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HERLOV LANGGÅRD AS

Org. no. 911825716 Limited company (AS) Fredrikstad Incorporated 1984 Active
Revenue 2025 NOK 2.0m
Operating profit NOK 740,000
Equity NOK 3.9m
Incorporated 1984
Share capital NOK 100,000

HERLOV LANGGÅRD AS is registered as a limited company in Fredrikstad, Østfold with organisation number 911825716. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1984. Registered share capital is NOK 100,000. The company's stated purpose is: “Drift av bok og accidenttrykkeri og dermed beslektet virksomhet, samt erverv og drift av fast eiendom. Videre ved aksjetegning eller på ennen måte gjøre seg interessert i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 740,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
▼ −6 %
Operating profit
NOK 740,000
▲ +90 %
Equity
NOK 3.9m
▲ +27 %
Est. value
NOK 4.8m

Financial health · 2025

Liquidity
2.75
Very good
Current assets ÷ current liabilities
Profitability
23.1%
Very good
Return on total assets
Solidity
85.3%
Very good
Equity as a share of total capital

Who owns HERLOV LANGGÅRD AS?

HERLOV LANGGÅRD AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about HERLOV LANGGÅRD AS

Who owns HERLOV LANGGÅRD AS?

Herlof Langgård is the largest registered owner, with 55.0%.

What is the revenue of HERLOV LANGGÅRD AS?

HERLOV LANGGÅRD AS had revenue of NOK 2.0m in 2025.

Who is the general manager of HERLOV LANGGÅRD AS?

Anne Langgård is registered as general manager of HERLOV LANGGÅRD AS.

Where is HERLOV LANGGÅRD AS based?

HERLOV LANGGÅRD AS has its business address in Fredrikstad.

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.