BIZTRAC BETA
COMPANY REGISTER PROFILE
989606379 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Rental and operating of own or leased real estate

LANGLIS VEI EIENDOM ANS

Org. no. 989606379 General partnership (ANS) Indre Østfold Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 483,000
Equity NOK 11.7m
Incorporated 1996

LANGLIS VEI EIENDOM ANS is registered as a general partnership in Indre Østfold, Østfold with organisation number 989606379. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. The company's stated purpose is: “Selskapets formål er for deltagernes felles regning og risiko å utnytte eiendommene Langlis vei 2, 4 og 4B i Spydeberg kommune gjennom virksomhet i form av utleie og for øvrig utnytte eiendommene på en best mulig måte. ”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 483,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 483,000
Equity
NOK 11.7m
Est. value
NOK 9.3m

Financial health · 2025

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

Who owns LANGLIS VEI EIENDOM ANS?

No shareholders are registered for LANGLIS VEI EIENDOM ANS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LANGLIS VEI EIENDOM ANS

What is the revenue of LANGLIS VEI EIENDOM ANS?

LANGLIS VEI EIENDOM ANS had revenue of NOK 2.4m in 2025.

Who is the general manager of LANGLIS VEI EIENDOM ANS?

Ove Brusegard is registered as general manager of LANGLIS VEI EIENDOM ANS.

Where is LANGLIS VEI EIENDOM ANS based?

LANGLIS VEI EIENDOM ANS has its business address in Spydeberg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.