biztrac. BETA
COMPANY REGISTER PROFILE
919932635 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

BERKÅK VEIKRO AS

Org. no. 919932635 Limited company (AS) Rennebu Incorporated 2017 Active
Revenue 2025 NOK 11.2m
Operating profit NOK 266,000
Equity NOK 1.0m
Incorporated 2017
Employees 9
Share capital NOK 100,000

BERKÅK VEIKRO AS is registered as a limited company in Rennebu, Trøndelag with organisation number 919932635. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Restaurant, veikro, utleie av motellrom og detaljhandel med drivstoff til motorvogner samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.2m in revenue and NOK 266,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.2m
▲ +13 %
Operating profit
NOK 266,000
▼ −74 %
Equity
NOK 1.0m
▼ −31 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
8.3%
Satisfactory
Return on total assets
Solidity
33.0%
Good
Equity as a share of total capital

Who owns BERKÅK VEIKRO AS?

BERKÅK VEIKRO AS
NOK 11.2m rev. · NOK 266,000 profit

BERKÅK VEIKRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERKÅK VEIKRO AS

Who owns BERKÅK VEIKRO AS?

NYBERG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BERKÅK VEIKRO AS?

BERKÅK VEIKRO AS had revenue of NOK 11.2m in 2025.

Who is the general manager of BERKÅK VEIKRO AS?

Anne Karin Nyberg is registered as general manager of BERKÅK VEIKRO AS.

Where is BERKÅK VEIKRO AS based?

BERKÅK VEIKRO AS has its business address in Rennebu.

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.