BIZTRAC BETA
COMPANY REGISTER PROFILE
980226867 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Farming of laying hens for production of eggs for consumption

GÅRDSMAT AS

Org. no. 980226867 Limited company (AS) Nærøysund Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 486,000
Equity NOK 972,000
Incorporated 1998
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-23 Aksjekapital registrert 2026-06-23.

GÅRDSMAT AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 980226867. The business is classified under farming of laying hens for production of eggs for consumption (NACE 01.471). The company was incorporated in 1998. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets formål er å selge næringsmidler samt annen virksomhet som kan gi tilleggsinntekt.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 486,000 in operating profit.

Former names: VIKNA BETONGSAGING AS

Key figures · 2025

Revenue
NOK 2.5m
▲ +16 %
Operating profit
NOK 486,000
▲ +210 %
Equity
NOK 972,000
▲ +63 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
5.00
Very good
Current assets ÷ current liabilities
Profitability
19.5%
Very good
Return on total assets
Solidity
36.0%
Good
Equity as a share of total capital

Who owns GÅRDSMAT AS?

GÅRDSMAT AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about GÅRDSMAT AS

Who owns GÅRDSMAT AS?

GAUTE HORSENG is the largest registered owner, with 60.0%.

What is the revenue of GÅRDSMAT AS?

GÅRDSMAT AS had revenue of NOK 2.5m in 2025.

Who is the general manager of GÅRDSMAT AS?

Paul Martin Wigdahl is registered as general manager of GÅRDSMAT AS.

Where is GÅRDSMAT AS based?

GÅRDSMAT AS has its business address in Rørvik.

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

Report a problem

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