BIZTRAC BETA
Beverage serving activities

FALSKE REKERS AKSJESELSKAP

Org. no. 926877933 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 138,000
Equity NOK 55,000
Incorporated 2021
Employees 31
Share capital NOK 30,000

FALSKE REKERS AKSJESELSKAP is registered as a limited company in Bergen, Vestland with organisation number 926877933. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2021 and has 31 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drift av baren FALSKE REKER.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 138,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 138,000
Equity
NOK 55,000
Est. value
NOK 537,000

Financial health · 2024

Liquidity
1.16
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.1%
Weak
Equity as a share of total capital

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

Who owns FALSKE REKERS AKSJESELSKAP?

CATHRINE TALLERAAS
FALSKE REKERS AKSJESELSKAP
NOK 3.6m rev. · NOK 138,000 profit

FALSKE REKERS AKSJESELSKAP has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FALSKE REKERS AKSJESELSKAP

Who owns FALSKE REKERS AKSJESELSKAP?

CATHRINE TALLERAAS is the largest registered owner, with 45.0%.

What is the revenue of FALSKE REKERS AKSJESELSKAP?

FALSKE REKERS AKSJESELSKAP had revenue of NOK 3.6m in 2024.

Who is the general manager of FALSKE REKERS AKSJESELSKAP?

Adrian Talleraas is registered as general manager of FALSKE REKERS AKSJESELSKAP.

Where is FALSKE REKERS AKSJESELSKAP based?

FALSKE REKERS AKSJESELSKAP has its business address in Bergen.

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.