BIZTRAC BETA
Uoppgitt

BARLUND GARD AS

Org. no. 931713159 Limited company (AS) Lom Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 140,000
Operating profit NOK 17,000
Equity NOK 27,000
Incorporated 2023
Share capital NOK 30,000

BARLUND GARD AS is registered as a limited company in Lom, Innlandet with organisation number 931713159. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 140,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 140,000
Operating profit
NOK 17,000
Equity
NOK 27,000
Est. value
NOK 91,000

Financial health · 2025

Liquidity
0.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BARLUND GARD AS?

KRISTOFFER BARLUND
BARLUND GARD AS
NOK 140,000 rev. · NOK 17,000 profit

BARLUND GARD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BARLUND GARD AS

Who owns BARLUND GARD AS?

KRISTOFFER BARLUND is the largest registered owner, with 100.0%.

What is the revenue of BARLUND GARD AS?

BARLUND GARD AS had revenue of NOK 140,000 in 2025.

Who is the general manager of BARLUND GARD AS?

Kristoffer Barlund is registered as general manager of BARLUND GARD AS.

Where is BARLUND GARD AS based?

BARLUND GARD AS has its business address in Lom.

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.